Remove stale mention of minimum master nodes check
This commit removes a stale mention of the minimum master nodes boostrap check from the docs. Relates #21653
This commit is contained in:
parent
407624c95a
commit
5ca60fa78b
|
@ -158,16 +158,15 @@ discovery.zen.ping.unicast.hosts:
|
||||||
=== `discovery.zen.minimum_master_nodes`
|
=== `discovery.zen.minimum_master_nodes`
|
||||||
|
|
||||||
To prevent data loss, it is vital to configure the
|
To prevent data loss, it is vital to configure the
|
||||||
`discovery.zen.minimum_master_nodes setting` so that each master-eligible node
|
`discovery.zen.minimum_master_nodes` setting so that each master-eligible node
|
||||||
knows the _minimum number of master-eligible nodes_ that must be visible in
|
knows the _minimum number of master-eligible nodes_ that must be visible in
|
||||||
order to form a cluster.
|
order to form a cluster.
|
||||||
|
|
||||||
Without this setting, a cluster that suffers a network failure is at risk of
|
Without this setting, a cluster that suffers a network failure is at risk of
|
||||||
having the cluster split into two independent clusters -- a split brain --
|
having the cluster split into two independent clusters -- a split brain --
|
||||||
which will lead to data loss. A more detailed explanation is provided
|
which will lead to data loss. A more detailed explanation is provided
|
||||||
in <<split-brain>>.
|
in <<split-brain>>.
|
||||||
|
|
||||||
|
|
||||||
To avoid a split brain, this setting should be set to a _quorum_ of master-
|
To avoid a split brain, this setting should be set to a _quorum_ of master-
|
||||||
eligible nodes:
|
eligible nodes:
|
||||||
|
|
||||||
|
@ -181,6 +180,3 @@ nodes should be set to `(3 / 2) + 1` or `2`:
|
||||||
discovery.zen.minimum_master_nodes: 2
|
discovery.zen.minimum_master_nodes: 2
|
||||||
--------------------------------------------------
|
--------------------------------------------------
|
||||||
|
|
||||||
IMPORTANT: If `discovery.zen.minimum_master_nodes` is not set when
|
|
||||||
Elasticsearch is running in <<dev-vs-prod,production mode>>, an exception will
|
|
||||||
be thrown which will prevent the node from starting.
|
|
||||||
|
|
Loading…
Reference in New Issue