# Cluster state yellow

**URL:** <https://discuss.elastic.co/t/cluster-state-yellow/15226>\
**Category:** Elasticsearch\
**Created:** [January 13, 2014, 9:30pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226 "2014-01-13T21:30:19Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![brian\_yoder](https://avatars.discourse-cdn.com/v4/letter/b/f1d935/32.png) [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)\
**Post date:** [January 14, 2014, 10:17pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/21 "2014-01-14T22:17:31Z")

</div>

> _Wouldn't the value increase as you add more nodes?_

Indeed, it most certainly will.

And with unicast discovery, each node will need to be told about the new  
node. Which is the perfect time to tell it about the newly calculated  
minimum number of masters.

Brian

--  
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/54e31afb-ea7f-4854-b970-f534505775cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/54e31afb-ea7f-4854-b970-f534505775cd%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Mohit\_Anchlia](https://avatars.discourse-cdn.com/v4/letter/m/848f3c/32.png) [@Mohit\_Anchlia](https://discuss.elastic.co/u/Mohit_Anchlia)\
**Post date:** [January 14, 2014, 10:48pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/22 "2014-01-14T22:48:43Z")

</div>

But today elasticsearch doesn't do this automatically?

On Tue, Jan 14, 2014 at 2:17 PM, InquiringMind [brian.from.fl@gmail.com](mailto:brian.from.fl@gmail.com)wrote:

> _Wouldn't the value increase as you add more nodes?_
> 
> Indeed, it most certainly will.
> 
> And with unicast discovery, each node will need to be told about the new  
> node. Which is the perfect time to tell it about the newly calculated  
> minimum number of masters.
> 
> Brian
> 
> --  
> 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/54e31afb-ea7f-4854-b970-f534505775cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/54e31afb-ea7f-4854-b970-f534505775cd%40googlegroups.com)  
> .
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CAOT3TWq\_iK7dFfooQt7HLgZ77WjhZUMV%3DDTtKOSEcU-fWK0-xw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAOT3TWq_iK7dFfooQt7HLgZ77WjhZUMV%3DDTtKOSEcU-fWK0-xw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 14, 2014, 10:58pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/23 "2014-01-14T22:58:45Z")

</div>

Nope.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 15 January 2014 09:48, Mohit Anchlia [mohitanchlia@gmail.com](mailto:mohitanchlia@gmail.com) wrote:

> But today elasticsearch doesn't do this automatically?
> 
> On Tue, Jan 14, 2014 at 2:17 PM, InquiringMind [brian.from.fl@gmail.com](mailto:brian.from.fl@gmail.com)wrote:
> 
> > _Wouldn't the value increase as you add more nodes?_
> > 
> > Indeed, it most certainly will.
> > 
> > And with unicast discovery, each node will need to be told about the new  
> > node. Which is the perfect time to tell it about the newly calculated  
> > minimum number of masters.
> > 
> > Brian
> > 
> > --  
> > 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/54e31afb-ea7f-4854-b970-f534505775cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/54e31afb-ea7f-4854-b970-f534505775cd%40googlegroups.com)  
> > .
> > 
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> 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/CAOT3TWq\_iK7dFfooQt7HLgZ77WjhZUMV%3DDTtKOSEcU-fWK0-xw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAOT3TWq_iK7dFfooQt7HLgZ77WjhZUMV%3DDTtKOSEcU-fWK0-xw%40mail.gmail.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CAEM624a-47F\_w7e0u2jaURfiPiHGL-p5M8-UD1qOe0bMqFKvuA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624a-47F_w7e0u2jaURfiPiHGL-p5M8-UD1qOe0bMqFKvuA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [January 14, 2014, 11:15pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/24 "2014-01-14T23:15:42Z")

</div>

Don't forget gateway.expected\_nodes 🙂

"Wouldn't the value increase as you add more nodes?"

It will, which is precisely why the value is not computed automatically.  
The value can decrease/increase over time, but the cluster does not know if  
this is because it is on purpose or because of failures. The suggested  
(n/2)+1 formula breaks down if n is constantly changing. With 10 nodes, it  
is suggested to use the value of 6 (10/2+1) for the minimum number of  
nodes. But if 5 nodes crash, then the suggested value is now 3 (5/2+1), but  
clearly 3 is not the value we want, we want 6.

Cheers,

Ivan

On Tue, Jan 14, 2014 at 2:58 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)wrote:

> Nope.
> 
> Regards,  
> Mark Walkom
> 
> Infrastructure Engineer  
> Campaign Monitor  
> email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
> web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
> 
> On 15 January 2014 09:48, Mohit Anchlia [mohitanchlia@gmail.com](mailto:mohitanchlia@gmail.com) wrote:
> 
> > But today elasticsearch doesn't do this automatically?
> > 
> > On Tue, Jan 14, 2014 at 2:17 PM, InquiringMind [brian.from.fl@gmail.com](mailto:brian.from.fl@gmail.com)wrote:
> > 
> > > _Wouldn't the value increase as you add more nodes?_
> > > 
> > > Indeed, it most certainly will.
> > > 
> > > And with unicast discovery, each node will need to be told about the new  
> > > node. Which is the perfect time to tell it about the newly calculated  
> > > minimum number of masters.
> > > 
> > > Brian
> > > 
> > > --  
> > > 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/54e31afb-ea7f-4854-b970-f534505775cd%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/54e31afb-ea7f-4854-b970-f534505775cd%40googlegroups.com)  
> > > .
> > > 
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > 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/CAOT3TWq\_iK7dFfooQt7HLgZ77WjhZUMV%3DDTtKOSEcU-fWK0-xw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAOT3TWq_iK7dFfooQt7HLgZ77WjhZUMV%3DDTtKOSEcU-fWK0-xw%40mail.gmail.com)  
> > .  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> 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/CAEM624a-47F\_w7e0u2jaURfiPiHGL-p5M8-UD1qOe0bMqFKvuA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624a-47F_w7e0u2jaURfiPiHGL-p5M8-UD1qOe0bMqFKvuA%40mail.gmail.com)  
> .
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CALY%3DcQCMrYAFBv%2BnRCMRYbev0bEaTPHswuUyEBsFvHS8XzKKvA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQCMrYAFBv%2BnRCMRYbev0bEaTPHswuUyEBsFvHS8XzKKvA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![brian\_yoder](https://avatars.discourse-cdn.com/v4/letter/b/f1d935/32.png) [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)\
**Post date:** [January 14, 2014, 11:35pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/25 "2014-01-14T23:35:47Z")

</div>

> _But today elasticsearch doesn't do this automatically?_

Short answer: No.  
Long answer: Nooooooooooooooooooooooooooooooooooooooo. _🙂_

For unicast discovery, you need to tell each node the full list of nodes in  
the cluster. As far as I can tell, that list may include the local node so  
it's easier to configure the same list everywhere. But it's not automatic.

For multicast discovery, it's automatic. But I've read enough about issues  
with multicast to want to stay with unicast.

Brian

--  
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/e2fc5288-9da9-412b-afc6-9e7ba923f7b6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e2fc5288-9da9-412b-afc6-9e7ba923f7b6%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [January 15, 2014, 7:39am UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/26 "2014-01-15T07:39:11Z")

</div>

It's not a a matter of unicast vs. multicast or failure vs. non-failure.

It's only the cluster admin who knows what the maximum number of nodes is.

For ES it is impossible to find that out during runtime, and therefore,  
minimum\_master\_nodes is a user defined setting.

Jörg

--  
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/CAKdsXoHGWAo6A6LK48%2BY0\_z2nysrjW\_jTud%2Bu1UEtJSJA-aUUA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHGWAo6A6LK48%2BY0_z2nysrjW_jTud%2Bu1UEtJSJA-aUUA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![brian\_yoder](https://avatars.discourse-cdn.com/v4/letter/b/f1d935/32.png) [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)\
**Post date:** [January 15, 2014, 4:17pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/27 "2014-01-15T16:17:42Z")

</div>

My apologies, Jörg, for being confusing.

_It's not a a matter of unicast vs. multicast or failure vs. non-failure._

> 

Indeed, the node count and minimum master count are independent of the  
discovery mechanism.

But the list of hostnames in the cluster is a matter of unicast; ES builds  
the list dynamically during multicast.

> _It's only the cluster admin who knows what the maximum number of nodes  
> is._

Exactly. So what I was trying to say is, if the cluster admin has to count  
all the nodes, the cluster admin might as well write down the hostnames  
too. And then the cluster admin can use Chef or Puppet to send the list of  
host names in a unicast configuration to all nodes.

And then my cool ES wrapper script picks up the list of hostnames, sets up  
the unicast discovery options using those names, automatically calculates  
the minimum number of nodes, and sets up that config option too. The ES  
starts with the best chance to prevent a split-brain situation.

I hope that is clearer.

As a follow on, one of the uses of ES is for a QA verification tool to  
emulate a production server but in a very lightweight (though fully  
functional) way. To that end, during the startup there is a preload step to  
ensure that a certain index is populated but to not reload if it already  
exists. And it uses the unicast host name list to determine that if there  
is only one host the preload step can be done automatically when the  
cluster first starts. But if there are two or more nodes in the cluster,  
the preload step is not done automatically.

One more reason to prefer unicast over multicast!

Brian

--  
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/9a177d63-fb9e-4e05-aefe-a9368d481021%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9a177d63-fb9e-4e05-aefe-a9368d481021%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [January 15, 2014, 5:15pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/28 "2014-01-15T17:15:27Z")

</div>

Unicast is a nightmare for large ES deployments, with provisioning and  
failures all the time. I'm used to DHCP/TFTP/PXE in my DC thanks to RedHat  
so why should I waste time setting up hostnames or count hosts for ES?

Jörg

On Wed, Jan 15, 2014 at 5:17 PM, InquiringMind [brian.from.fl@gmail.com](mailto:brian.from.fl@gmail.com)wrote:

> One more reason to prefer unicast over multicast!

--  
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/CAKdsXoGdS1h-f85Tk-h8SBY92eqfXEvrGV6E0sqPNwkbXrfaxA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGdS1h-f85Tk-h8SBY92eqfXEvrGV6E0sqPNwkbXrfaxA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Mohit\_Anchlia](https://avatars.discourse-cdn.com/v4/letter/m/848f3c/32.png) [@Mohit\_Anchlia](https://discuss.elastic.co/u/Mohit_Anchlia)\
**Post date:** [January 15, 2014, 5:49pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/29 "2014-01-15T17:49:41Z")

</div>

IMHO I think ES can still be smart enough to calculate that formula  
dynamically since it knows when servers are being added to the cluster,  
correct? As for the node crash it's still a crash and if user wants to  
decomission the node then the better way would be to explicitly run a  
decomission command to indicate that nodes is not part of cluster anymore?  
Is there any problem with this logic?

On Wed, Jan 15, 2014 at 9:15 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<  
[joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote:

> Unicast is a nightmare for large ES deployments, with provisioning and  
> failures all the time. I'm used to DHCP/TFTP/PXE in my DC thanks to RedHat  
> so why should I waste time setting up hostnames or count hosts for ES?
> 
> Jörg
> 
> On Wed, Jan 15, 2014 at 5:17 PM, InquiringMind [brian.from.fl@gmail.com](mailto:brian.from.fl@gmail.com)wrote:
> 
> > One more reason to prefer unicast over multicast!
> > 
> > --  
> > 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/CAKdsXoGdS1h-f85Tk-h8SBY92eqfXEvrGV6E0sqPNwkbXrfaxA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGdS1h-f85Tk-h8SBY92eqfXEvrGV6E0sqPNwkbXrfaxA%40mail.gmail.com)  
> > .
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CAOT3TWoCEg%3DL-wDNXR1mFFScDZT%2BTxUsAoyBZ31OHoLtEyo6uA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAOT3TWoCEg%3DL-wDNXR1mFFScDZT%2BTxUsAoyBZ31OHoLtEyo6uA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [January 15, 2014, 6:24pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/30 "2014-01-15T18:24:17Z")

</div>

If the current node count is always assumed as maximum count, the  
minimum\_master\_node condition N+1/2 would never be met ☹

What you surely mean instead is that ES should remember cluster node count  
over time, and keeps the max value as the value for the formula. But that  
would mean you must not add nodes for spare which is also irritating, and  
the formula of N+1/2 must be the one and only true formula. But N+1/2  
could be tightened to stronger split-brain risk mitigation - there is no  
reason why minimum\_master\_node should not be set to N so a cluster must  
always find all nodes before master election.

Jörg

--  
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/CAKdsXoGCJvs2-B%3Ddn3g52uM46Y7KvTAkS0dWS8%3DCDvYhBFyHXw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGCJvs2-B%3Ddn3g52uM46Y7KvTAkS0dWS8%3DCDvYhBFyHXw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![brian\_yoder](https://avatars.discourse-cdn.com/v4/letter/b/f1d935/32.png) [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)\
**Post date:** [January 15, 2014, 6:50pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/31 "2014-01-15T18:50:15Z")

</div>

Jörg

I avoided multicast and preferred unicast based on many discussions in the  
newsgroups and other sites. In particular, the Elasticsearch Preflight  
Checklist[http://asquera.de/opensource/2012/11/25/elasticsearch-pre-flight-checklist/](http://asquera.de/opensource/2012/11/25/elasticsearch-pre-flight-checklist/).  
Within this checklist, the sections entitled DISCOVERY and AVOIDING  
SPLIT-BRAINS were the recommendationsI that I followed. This write-up  
didn't say that mutlicast was bad, but neither have I read before that  
unicast was a nightmare.

Whenever you get a chance, if you could describe the provisioning issues  
and failures, that would help to shed some more light on this subject.

And it does seem that somebody needs to waste time counting hosts. You  
stated (and I agree) that minimum\_master\_nodes must be set to N/2 + 1, and  
N must be specified by the system admin... via counting? Or is there  
something else I am not seeing?

Brian

On Wednesday, January 15, 2014 12:15:27 PM UTC-5, Jörg Prante wrote:

> Unicast is a nightmare for large ES deployments, with provisioning and  
> failures all the time. I'm used to DHCP/TFTP/PXE in my DC thanks to RedHat  
> so why should I waste time setting up hostnames or count hosts for ES?
> 
> Jörg

--  
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/4353c8da-b73e-4175-a083-a80ea3d65f69%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4353c8da-b73e-4175-a083-a80ea3d65f69%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [January 15, 2014, 7:17pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/32 "2014-01-15T19:17:30Z")

</div>

The preflight checklist is misleading in several statements:

- you can not "accidentally join" clusters because of multicast. It happens  
when using the default cluster name

- "a lot of chatter with no use" is just pure ignorance of network  
technology. Multicast was designed for zero config, and I love ES for zero  
config. And there is no chatter if you set up a private network for ES  
hosts. That is simple with a router/switch and DHCP. Whole corporation and  
datacenter networks can not live without link-local config for example.

- "you don't have to include the whole cluster" is misleading - each data  
node must always be able to connect to one of the eligible master nodes, or  
the cluster may not work correctly

- the "avoiding split brain" section is a very bold and wrong headline. It  
is promising that split-brains can be avoided by a N/2+1 setting.  
Unfortunately that is nonsense, the truth is, it lowers the risk  
significantly. But there can still be obscure network splits where two  
halves of a split cluster may overlap, so the condition of N/2+1 can become  
true for both halves.

Why do I not count hosts/nodes? There is a difference between the number of  
data nodes and master eligible nodes in a cluster. I have three master  
eligible nodes and set minimum\_master\_nodes to 3, and that's it. After that  
I can start or stop additional data nodes as much as I like.

Jörg

--  
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/CAKdsXoG8Yi8KuG7%2BYa3HQEAj%2BDhPUvzoqd6aR-Gpd4iQxAF%3D%2Bw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8Yi8KuG7%2BYa3HQEAj%2BDhPUvzoqd6aR-Gpd4iQxAF%3D%2Bw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![brian\_yoder](https://avatars.discourse-cdn.com/v4/letter/b/f1d935/32.png) [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)\
**Post date:** [January 15, 2014, 8:07pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/33 "2014-01-15T20:07:03Z")

</div>

Thank you very much, Jörg. Your explanation is clear and concise and  
greatly improves my understanding!

Brian

--  
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/18afbcfe-fcd1-47e9-91cb-a617dc089abf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/18afbcfe-fcd1-47e9-91cb-a617dc089abf%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Mohit\_Anchlia](https://avatars.discourse-cdn.com/v4/letter/m/848f3c/32.png) [@Mohit\_Anchlia](https://discuss.elastic.co/u/Mohit_Anchlia)\
**Post date:** [January 15, 2014, 8:59pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/34 "2014-01-15T20:59:32Z")

</div>

IHO, I think there is no perfect solution for any of the complex  
network issues, however if we know of a config that reduces the risk  
signficantly then I think we should adopt that as a default config.

On Wed, Jan 15, 2014 at 11:17 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<  
[joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote:

> The preflight checklist is misleading in several statements:
> 
> - you can not "accidentally join" clusters because of multicast. It  
> happens when using the default cluster name
> 
> - "a lot of chatter with no use" is just pure ignorance of network  
> technology. Multicast was designed for zero config, and I love ES for zero  
> config. And there is no chatter if you set up a private network for ES  
> hosts. That is simple with a router/switch and DHCP. Whole corporation and  
> datacenter networks can not live without link-local config for example.
> 
> - "you don't have to include the whole cluster" is misleading - each data  
> node must always be able to connect to one of the eligible master nodes, or  
> the cluster may not work correctly
> 
> - the "avoiding split brain" section is a very bold and wrong headline. It  
> is promising that split-brains can be avoided by a N/2+1 setting.  
> Unfortunately that is nonsense, the truth is, it lowers the risk  
> significantly. But there can still be obscure network splits where two  
> halves of a split cluster may overlap, so the condition of N/2+1 can become  
> true for both halves.
> 
> Why do I not count hosts/nodes? There is a difference between the number  
> of data nodes and master eligible nodes in a cluster. I have three master  
> eligible nodes and set minimum\_master\_nodes to 3, and that's it. After that  
> I can start or stop additional data nodes as much as I like.
> 
> Jörg
> 
> --  
> 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/CAKdsXoG8Yi8KuG7%2BYa3HQEAj%2BDhPUvzoqd6aR-Gpd4iQxAF%3D%2Bw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8Yi8KuG7%2BYa3HQEAj%2BDhPUvzoqd6aR-Gpd4iQxAF%3D%2Bw%40mail.gmail.com)  
> .
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CAOT3TWoibQk\_0o313aXEwYkbYrQiVnmgrp4eNnOMTurmCS6PPw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAOT3TWoibQk_0o313aXEwYkbYrQiVnmgrp4eNnOMTurmCS6PPw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [January 15, 2014, 9:06pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/35 "2014-01-15T21:06:46Z")

</div>

We use mutlicast but our networks are very we're pretty used to multicast  
for other stuff like varnish cache flushes. I figured unicast vs multicast  
was a networking decision based on how your data center is rigged. No one  
has complained about chatter and we've never seen a problem with accidental  
joining. We keep the cluster names distinct even for networks that we  
imagine aren't flat from a multicast perspective.

Nik

On Wed, Jan 15, 2014 at 3:59 PM, Mohit Anchlia [mohitanchlia@gmail.com](mailto:mohitanchlia@gmail.com)wrote:

> IHO, I think there is no perfect solution for any of the complex  
> network issues, however if we know of a config that reduces the risk  
> signficantly then I think we should adopt that as a default config.
> 
> On Wed, Jan 15, 2014 at 11:17 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<  
> [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote:
> 
> > The preflight checklist is misleading in several statements:
> > 
> > - you can not "accidentally join" clusters because of multicast. It  
> > happens when using the default cluster name
> > 
> > - "a lot of chatter with no use" is just pure ignorance of network  
> > technology. Multicast was designed for zero config, and I love ES for zero  
> > config. And there is no chatter if you set up a private network for ES  
> > hosts. That is simple with a router/switch and DHCP. Whole corporation and  
> > datacenter networks can not live without link-local config for example.
> > 
> > - "you don't have to include the whole cluster" is misleading - each data  
> > node must always be able to connect to one of the eligible master nodes, or  
> > the cluster may not work correctly
> > 
> > - the "avoiding split brain" section is a very bold and wrong headline.  
> > It is promising that split-brains can be avoided by a N/2+1 setting.  
> > Unfortunately that is nonsense, the truth is, it lowers the risk  
> > significantly. But there can still be obscure network splits where two  
> > halves of a split cluster may overlap, so the condition of N/2+1 can become  
> > true for both halves.
> > 
> > Why do I not count hosts/nodes? There is a difference between the number  
> > of data nodes and master eligible nodes in a cluster. I have three master  
> > eligible nodes and set minimum\_master\_nodes to 3, and that's it. After that  
> > I can start or stop additional data nodes as much as I like.
> > 
> > Jörg
> > 
> > --  
> > 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/CAKdsXoG8Yi8KuG7%2BYa3HQEAj%2BDhPUvzoqd6aR-Gpd4iQxAF%3D%2Bw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoG8Yi8KuG7%2BYa3HQEAj%2BDhPUvzoqd6aR-Gpd4iQxAF%3D%2Bw%40mail.gmail.com)  
> > .
> > 
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> 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/CAOT3TWoibQk\_0o313aXEwYkbYrQiVnmgrp4eNnOMTurmCS6PPw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAOT3TWoibQk_0o313aXEwYkbYrQiVnmgrp4eNnOMTurmCS6PPw%40mail.gmail.com)  
> .
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CAPmjWd198GpnLrTpkFRLzWgZApEiEBqq2-h--GTTUZCQNH4ykA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd198GpnLrTpkFRLzWgZApEiEBqq2-h--GTTUZCQNH4ykA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [January 15, 2014, 9:55pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/36 "2014-01-15T21:55:21Z")

</div>

Using quorum consensus (another name for the 'minimum\_master\_node'  
approach) as default is not possible, since the quorum count is only known  
by the admin.

There are perfect solutions for consensus but they are not easy to  
implement, see Byzantine fault tolerance

> **[Byzantine fault tolerance](https://en.wikipedia.org/wiki/Byzantine_fault_tolerance)**
>
> Byzantine fault tolerance (BFT) is the resistance of a fault-tolerant computer system, particularly distributed computing systems, towards electronic component failures where there is imperfect information on whether a component is failed. In a "Byzantine failure", a component such as a server can inconsistently appear both failed and functioning to failure detection systems, presenting different symptoms to different observers. It is difficult for the other components to declare it failed and sh...

or Paxos

[http://research.google.com/archive/paxos\_made\_live.html](http://research.google.com/archive/paxos_made_live.html)

or a more promising approach started lately, RAFT

[http://raftconsensus.github.io/](http://raftconsensus.github.io/)

Jörg

--  
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/CAKdsXoH4FFgKVeJY37aRuurAt7To5jLa%3D0Rp3b--AcGE%3DhEqoA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH4FFgKVeJY37aRuurAt7To5jLa%3D0Rp3b--AcGE%3DhEqoA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Norberto\_Meijome](https://avatars.discourse-cdn.com/v4/letter/n/ed655f/32.png) [@Norberto\_Meijome](https://discuss.elastic.co/u/Norberto_Meijome)\
**Post date:** [January 16, 2014, 8:01am UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/37 "2014-01-16T08:01:37Z")

</div>

Great thread, thanks.

Some points: just because you know how many ( master ) nodes you have  
doesn't mean you know or should care about their hostnames ; ec2 . servers  
are cattle not pets, etc.

One thing I am not sure about. Would it be possible ( ie , safe) to make  
the quorum threshold a runtime configurable value, rather than having to  
restart all the nodes for the change to take effect? We'd have to put some  
code around this for safety of course ( what happens if you set a number \>  
N, for example...)

Also,can anyone comment on using zookeeper for master choosing ( and cfg  
updates?) . I saw a plugin for zk but haven't had time to test.

Thanks !  
Beto  
On 16/01/2014 8:55 AM, "[joergprante@gmail.com](mailto:joergprante@gmail.com)" [joergprante@gmail.com](mailto:joergprante@gmail.com)  
wrote:

> Using quorum consensus (another name for the 'minimum\_master\_node'  
> approach) as default is not possible, since the quorum count is only known  
> by the admin.
> 
> There are perfect solutions for consensus but they are not easy to  
> implement, see Byzantine fault tolerance
> 
> [Byzantine fault - Wikipedia](http://en.wikipedia.org/wiki/Byzantine_fault_tolerance)
> 
> or Paxos
> 
> [Paxos Made Live - An Engineering Perspective (2006 Invited Talk) – Google Research](http://research.google.com/archive/paxos_made_live.html)
> 
> or a more promising approach started lately, RAFT
> 
> [http://raftconsensus.github.io/](http://raftconsensus.github.io/)
> 
> Jörg
> 
> --  
> 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/CAKdsXoH4FFgKVeJY37aRuurAt7To5jLa%3D0Rp3b--AcGE%3DhEqoA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH4FFgKVeJY37aRuurAt7To5jLa%3D0Rp3b--AcGE%3DhEqoA%40mail.gmail.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CACj2-4JU-J7\_in1iMfP2x7kxZn-OJBWfWJFy1ME%2B%2Bd4gSOH2kw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACj2-4JU-J7_in1iMfP2x7kxZn-OJBWfWJFy1ME%2B%2Bd4gSOH2kw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [January 16, 2014, 1:43pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/38 "2014-01-16T13:43:40Z")

</div>

minimum\_master\_nodes is a dynamic cluster setting, that means, it can be  
set via cluster update API.

Jörg

--  
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/CAKdsXoHFgi5Wj%2Bz0P%2Bq3AJj55bTjaNhjGAzj\_DHPmVfq6iRpBQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHFgi5Wj%2Bz0P%2Bq3AJj55bTjaNhjGAzj_DHPmVfq6iRpBQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Norberto\_Meijome](https://avatars.discourse-cdn.com/v4/letter/n/ed655f/32.png) [@Norberto\_Meijome](https://discuss.elastic.co/u/Norberto_Meijome)\
**Post date:** [January 16, 2014, 2:08pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/39 "2014-01-16T14:08:51Z")

</div>

Gotcha, my bad.  
On 17/01/2014 12:43 AM, "[joergprante@gmail.com](mailto:joergprante@gmail.com)" [joergprante@gmail.com](mailto:joergprante@gmail.com)  
wrote:

> minimum\_master\_nodes is a dynamic cluster setting, that means, it can be  
> set via cluster update API.
> 
> Jörg
> 
> --  
> 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/CAKdsXoHFgi5Wj%2Bz0P%2Bq3AJj55bTjaNhjGAzj\_DHPmVfq6iRpBQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHFgi5Wj%2Bz0P%2Bq3AJj55bTjaNhjGAzj_DHPmVfq6iRpBQ%40mail.gmail.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CACj2-4JfuGA4wAmTCjMdo2T%2B4cuY96EV1EN3Grc-pDMt%3D3xX%3DA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACj2-4JfuGA4wAmTCjMdo2T%2B4cuY96EV1EN3Grc-pDMt%3D3xX%3DA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Mohit\_Anchlia](https://avatars.discourse-cdn.com/v4/letter/m/848f3c/32.png) [@Mohit\_Anchlia](https://discuss.elastic.co/u/Mohit_Anchlia)\
**Post date:** [February 3, 2014, 10:19pm UTC](https://discuss.elastic.co/t/cluster-state-yellow/15226/40 "2014-02-03T22:19:09Z")

</div>

How does minimum\_master\_nodes differ from action.write\_consistency? Would  
setting write\_consistency to quorum help when minimum\_master is not set  
appropriately?  
On Thu, Jan 16, 2014 at 6:08 AM, Norberto Meijome [numard@gmail.com](mailto:numard@gmail.com) wrote:

> Gotcha, my bad.  
> On 17/01/2014 12:43 AM, "[joergprante@gmail.com](mailto:joergprante@gmail.com)" [joergprante@gmail.com](mailto:joergprante@gmail.com)  
> wrote:
> 
> > minimum\_master\_nodes is a dynamic cluster setting, that means, it can be  
> > set via cluster update API.
> > 
> > Jörg
> > 
> > --  
> > 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/CAKdsXoHFgi5Wj%2Bz0P%2Bq3AJj55bTjaNhjGAzj\_DHPmVfq6iRpBQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHFgi5Wj%2Bz0P%2Bq3AJj55bTjaNhjGAzj_DHPmVfq6iRpBQ%40mail.gmail.com)  
> > .  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> 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/CACj2-4JfuGA4wAmTCjMdo2T%2B4cuY96EV1EN3Grc-pDMt%3D3xX%3DA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACj2-4JfuGA4wAmTCjMdo2T%2B4cuY96EV1EN3Grc-pDMt%3D3xX%3DA%40mail.gmail.com)  
> .
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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/CAOT3TWrGJHi\_R\_WXquKD-GmYv\_fojs23h%2B-rBs-NZxNSznQwmQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAOT3TWrGJHi_R_WXquKD-GmYv_fojs23h%2B-rBs-NZxNSznQwmQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

[Previous page](https://discuss.elastic.co/t/cluster-state-yellow/15226.md?page=1)

[Next page](https://discuss.elastic.co/t/cluster-state-yellow/15226.md?page=3)
