Removal of discovery.zen.minimum_master_nodes

As described in, discovery.zen.minimum_master_nodes option is ingored in 7.0 version.

But this setting was earlier used to avoid a split brain situation by setting to (1+(m/2)) where m is the number of master-eligible nodes in the cluster.

If this setting is now ignored, has ES become susceptible to split brain?
Or internally, the above setting is being set to ((1+(m/2)) ?
Some more documentation on the above link would have been very helpful.


@sg.esearch Check out our blog post on this topic.

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.