-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[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
Conversation
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] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this 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] |
There was a problem hiding this comment.
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.
Thanks @nik9000 ! |
There was a problem hiding this 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 |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -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] |
There was a problem hiding this 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 page & the fact that we only publish one version of it, this is a case where linking to current makes sense.
There was a problem hiding this 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.
* [DOCS] Remove references to deprecated 'zen.discovery.minimum_master_nodes' setting
* [DOCS] Remove references to deprecated 'zen.discovery.minimum_master_nodes' setting
* [DOCS] Remove references to deprecated 'zen.discovery.minimum_master_nodes' setting
Fixes two broken links in Elasticsearch Resiliency Status for v7.0 release.