File tree Expand file tree Collapse file tree 1 file changed +2
-2
lines changed
docs/reference/modules/discovery Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -75,7 +75,7 @@ The `discovery.zen.minimum_master_nodes` sets the minimum
7575number of master eligible nodes that need to join a newly elected master in order for an election to
7676complete and for the elected node to accept its mastership. The same setting controls the minimum number of
7777active master eligible nodes that should be a part of any active cluster. If this requirement is not met the
78- active master node will step down and a new master election will be begin.
78+ active master node will step down and a new master election will begin.
7979
8080This setting must be set to a quorum of your master eligible nodes. It is recommended to avoid
8181having only two master eligible nodes, since a quorum of two is two. Therefore, a loss
@@ -140,7 +140,7 @@ The `discovery.zen.no_master_block` setting has two valid options:
140140`all`:: All operations on the node--i.e. both read & writes--will be rejected. This also applies for api cluster state
141141read or write operations, like the get index settings, put mapping and cluster state api.
142142`write`:: (default) Write operations will be rejected. Read operations will succeed, based on the last known cluster configuration.
143- This may result in partial reads of stale data as this node may be isolated from the rest of the cluster.
143+ This may result in partial reads of stale data as this node may be isolated from the rest of the cluster.
144144
145145The `discovery.zen.no_master_block` setting doesn't apply to nodes-based apis (for example cluster stats, node info and
146146node stats apis). Requests to these apis will not be blocked and can run on any available node.
You can’t perform that action at this time.
0 commit comments