# Minimum\_master\_nodes is explained conflict in elasticsearch.yml and Guide docs

**URL:** <https://discuss.elastic.co/t/minimum-master-nodes-is-explained-conflict-in-elasticsearch-yml-and-guide-docs/14835>\
**Category:** Elasticsearch\
**Created:** [December 12, 2013, 9:08am UTC](https://discuss.elastic.co/t/minimum-master-nodes-is-explained-conflict-in-elasticsearch-yml-and-guide-docs/14835 "2013-12-12T09:08:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![liangwb2001](https://avatars.discourse-cdn.com/v4/letter/l/57b2e6/32.png) [@liangwb2001](https://discuss.elastic.co/u/liangwb2001)\
**Post date:** [December 12, 2013, 9:08am UTC](https://discuss.elastic.co/t/minimum-master-nodes-is-explained-conflict-in-elasticsearch-yml-and-guide-docs/14835/1 "2013-12-12T09:08:05Z")

</div>

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:](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](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](http://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](mailto: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](https://groups.google.com/d/msgid/elasticsearch/1386839285618-4045933.post%40n3.nabble.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 2:01am UTC](https://discuss.elastic.co/t/minimum-master-nodes-is-explained-conflict-in-elasticsearch-yml-and-guide-docs/14835/2 "2017-07-06T02:01:43Z")

</div>