Skip to content

Commit 154d388

Browse files
committed
Reinstate recommendation for ≥ 3 master-eligible nodes. (#27204)
In the docs for 1.7 ([doc][doc-1.7], [src][src-1.7]) there was a recommendation for at least 3 master-eligible nodes "in critical clusters" but this was lost when that page was updated in 2.0 ([doc][doc-2.0], [src][src-2.0]). I'd like to reinstate this. [doc-1.7]: https://www.elastic.co/guide/en/elasticsearch/reference/1.7/modules-node.html [src-1.7]: https://github.com/elastic/elasticsearch/blob/2cbaccb2f2a495923bc64447fe3396e0fc58b3d3/docs/reference/modules/node.asciidoc [doc-2.0]: https://www.elastic.co/guide/en/elasticsearch/reference/2.0/modules-node.html#split-brain [src-2.0]: https://github.com/elastic/elasticsearch/blob/4799009ad7ea8f885b6aedc6f62ad61d69e7a40d/docs/reference/modules/node.asciidoc
1 parent 8b49a5a commit 154d388

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

docs/reference/modules/node.asciidoc

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -156,6 +156,13 @@ discovery.zen.minimum_master_nodes: 2 <1>
156156
----------------------------
157157
<1> Defaults to `1`.
158158

159+
To be able to remain available when one of the master-eligible nodes fails,
160+
clusters should have at least three master-eligible nodes, with
161+
`minimum_master_nodes` set accordingly. A <<rolling-upgrades,rolling upgrade>>,
162+
performed without any downtime, also requires at least three master-eligible
163+
nodes to avoid the possibility of data loss if a network split occurs while the
164+
upgrade is in progress.
165+
159166
This setting can also be changed dynamically on a live cluster with the
160167
<<cluster-update-settings,cluster update settings API>>:
161168

0 commit comments

Comments
 (0)