Minimum_master_nodes is explained conflict in elasticsearch.yml and Guide docs


(liangwb2001) #1

Hi, the minimum_master_nodes option's annotation in elasticsearch.yml:
#Set to ensure a node sees N other master eligible nodes to be considered
operational within the cluster. Set this option to a higher value (2-4) for
large clusters (>3 nodes).

 it means minimum_master_nodes not include current node self. so

minimum_master_nodes=N/2;

but in
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html#master-election:
#The discovery.zen.minimum_master_nodes allows to control the minimum
number of master eligible nodes a node should "see" in order to operate
within the cluster. Its recommended to set it to a higher value than 1 when
running more than 2 nodes in the cluster.

it means minimum_master_nodes should include current node self. so

minimum_master_nodes=(N/2+1);

AnyOne tell me which is right?

--
View this message in context: http://elasticsearch-users.115913.n3.nabble.com/minimum-master-nodes-is-explained-conflict-in-elasticsearch-yml-and-Guide-docs-tp4045933.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1386839285618-4045933.post%40n3.nabble.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #2