Skip to content

[DOCS] Fix broken links for 7.0 release #41036

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 9, 2019
Merged

[DOCS] Fix broken links for 7.0 release #41036

merged 2 commits into from
Apr 9, 2019

Conversation

jrodewig
Copy link
Contributor

@jrodewig jrodewig commented Apr 9, 2019

Fixes two broken links in Elasticsearch Resiliency Status for v7.0 release.

@jrodewig jrodewig added >docs General docs changes :Core/Infra/Resiliency Keep running when everything is ok. Die quickly if things go horribly wrong. v8.0.0 v7.2.0 v7.0.1 labels Apr 9, 2019
@jrodewig jrodewig requested review from debadair and lcawl April 9, 2019 21:16
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@@ -279,7 +279,7 @@ shard will be allocated upon reopening the index.
[float]
=== Use two phase commit for Cluster State publishing (STATUS: DONE, v5.0.0)

A master node in Elasticsearch continuously https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-zen.html#fault-detection[monitors the cluster nodes]
A master node in Elasticsearch continuously https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-fault-detection.html[monitors the cluster nodes]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lcawl @debadair

Based on my local doc builds, it doesn't look like we can use attributes like {ref} here. Let me know if that's not the case.

If not, I'll create a separate issue to include those attributes and fix up this link. I didn't want to hold this fix up in the meantime.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't believe we have those attributes set up, no.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's just a matter of including the shared attributes...but I agree that it's not essential.

Copy link
Member

@nik9000 nik9000 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -279,7 +279,7 @@ shard will be allocated upon reopening the index.
[float]
=== Use two phase commit for Cluster State publishing (STATUS: DONE, v5.0.0)

A master node in Elasticsearch continuously https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-zen.html#fault-detection[monitors the cluster nodes]
A master node in Elasticsearch continuously https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-fault-detection.html[monitors the cluster nodes]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't believe we have those attributes set up, no.

@jrodewig
Copy link
Contributor Author

jrodewig commented Apr 9, 2019

Thanks @nik9000 !

Copy link
Contributor

@debadair debadair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Due to the nature of the resiliency status page and the fact that we publish a single version of it, this is one of those rare cases where linking to "current" seems like the right thing to do.

@@ -296,7 +296,7 @@ the change, it is committed and commit messages are sent to the nodes. See {GIT}

During master election each node pings in order to discover other nodes and validate the liveness of existing
nodes. Based on this information the node either discovers an existing master or, if enough nodes are found
(see https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-zen.html#master-election[`discovery.zen.minimum_master_nodes`]) a new master will be elected. Currently, the node that is
(`discovery.zen.minimum_master_nodes`) a new master will be elected. Currently, the node that is
elected as master will update the cluster state to indicate the result of the election. Other nodes will submit
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discovery has changed in 7.0 and the referenced setting is deprecated. Rather than simply removing the link, I'd remove the references to the discovery.zen.minimum_master_nodes setting and cross reference https://www.elastic.co/guide/en/elasticsearch/reference/7.0/modules-discovery-quorums.html#_master_elections for more information.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @debadair! I removed those references with 2d4aef6.

@@ -279,7 +279,7 @@ shard will be allocated upon reopening the index.
[float]
=== Use two phase commit for Cluster State publishing (STATUS: DONE, v5.0.0)

A master node in Elasticsearch continuously https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-zen.html#fault-detection[monitors the cluster nodes]
A master node in Elasticsearch continuously https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-fault-detection.html[monitors the cluster nodes]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Due to the nature of the Resiliency page & the fact that we only publish one version of it, this is a case where linking to current makes sense.

Copy link
Contributor

@debadair debadair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to revisit the Resiliency Guide in general when the 7.0 dust settles.

@jrodewig jrodewig merged commit e3f7143 into elastic:master Apr 9, 2019
@jrodewig jrodewig deleted the fix-broken-7.0-links branch April 9, 2019 22:18
jrodewig added a commit that referenced this pull request Apr 9, 2019
* [DOCS] Remove references to deprecated 'zen.discovery.minimum_master_nodes' setting
jrodewig added a commit that referenced this pull request Apr 9, 2019
* [DOCS] Remove references to deprecated 'zen.discovery.minimum_master_nodes' setting
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this pull request May 27, 2019
* [DOCS] Remove references to deprecated 'zen.discovery.minimum_master_nodes' setting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Resiliency Keep running when everything is ok. Die quickly if things go horribly wrong. >docs General docs changes v7.0.1 v7.2.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants