# Discovery.zen.minimum\_master\_nodes and gateway.recover\_after\_nodes does not work after upgrading to ES 1.0.1?

**URL:** https://discuss.elastic.co/t/discovery-zen-minimum-master-nodes-and-gateway-recover-after-nodes-does-not-work-after-upgrading-to-es-1-0-1/16626
**Category:** Elasticsearch
**Created:** [March 26, 2014, 8:00pm UTC](https://discuss.elastic.co/t/discovery-zen-minimum-master-nodes-and-gateway-recover-after-nodes-does-not-work-after-upgrading-to-es-1-0-1/16626 "2014-03-26T20:00:14Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![David\_Smith\_2](https://avatars.discourse-cdn.com/v4/letter/d/a9a28c/32.png) [@David\_Smith\_2](https://discuss.elastic.co/u/David_Smith_2)
#### Post date: [March 26, 2014, 8:00pm UTC](https://discuss.elastic.co/t/discovery-zen-minimum-master-nodes-and-gateway-recover-after-nodes-does-not-work-after-upgrading-to-es-1-0-1/16626/1 "2014-03-26T20:00:14Z")

</div>

We have 16 node cluster on 0.90.5. We built a new cluster for 1.0.1 (yes,  
we will upgrade to 1.1.0 soon) but we experience this problem that I would  
like help with.

In our 0.90.5 cluster, we had it configured as:

discovery.zen.minimum\_master\_nodes: 9  
gateway.expected\_nodes: 16  
gateway.recover\_after\_nodes: 12

But when we built the 1.0.1 cluster with the same settings, all the nodes  
return 503 when upon startup after checking status [http://localhost:9200](http://localhost:9200).

Had to turn that down as below to get it working and return 200 status as  
usual.  
discovery.zen.minimum\_master\_nodes: 1

gateway.expected\_nodes: 16  
gateway.recover\_after\_nodes: 1

Full elasticsearch yaml configs for both clusters  
are: [https://gist.github.com/ppat/9791741](https://gist.github.com/ppat/9791741)

Am I doing anything wrong? Or is this an issue?

--  
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/a1a63c2e-5717-4cb4-b10f-323ccd37f2fc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a1a63c2e-5717-4cb4-b10f-323ccd37f2fc%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![David\_Smith\_2](https://avatars.discourse-cdn.com/v4/letter/d/a9a28c/32.png) [@David\_Smith\_2](https://discuss.elastic.co/u/David_Smith_2)
#### Post date: [March 27, 2014, 8:27pm UTC](https://discuss.elastic.co/t/discovery-zen-minimum-master-nodes-and-gateway-recover-after-nodes-does-not-work-after-upgrading-to-es-1-0-1/16626/2 "2014-03-27T20:27:47Z")

</div>

Anybody? Help?

On Wednesday, March 26, 2014 4:00:14 PM UTC-4, David Smith wrote:

> We have 16 node cluster on 0.90.5. We built a new cluster for 1.0.1 (yes,  
> we will upgrade to 1.1.0 soon) but we experience this problem that I would  
> like help with.
> 
> In our 0.90.5 cluster, we had it configured as:
> 
> discovery.zen.minimum\_master\_nodes: 9  
> gateway.expected\_nodes: 16  
> gateway.recover\_after\_nodes: 12
> 
> But when we built the 1.0.1 cluster with the same settings, all the nodes  
> return 503 when upon startup after checking status [http://localhost:9200](http://localhost:9200).
> 
> Had to turn that down as below to get it working and return 200 status as  
> usual.  
> discovery.zen.minimum\_master\_nodes: 1
> 
> gateway.expected\_nodes: 16  
> gateway.recover\_after\_nodes: 1
> 
> Full elasticsearch yaml configs for both clusters are:  
> [elasticsearch.yml for 0.90.5 clustr · GitHub](https://gist.github.com/ppat/9791741)
> 
> Am I doing anything wrong? Or is this an issue?

--  
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/93df5ea3-6638-4ebd-a8ef-453736f07f32%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/93df5ea3-6638-4ebd-a8ef-453736f07f32%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 1:40am UTC](https://discuss.elastic.co/t/discovery-zen-minimum-master-nodes-and-gateway-recover-after-nodes-does-not-work-after-upgrading-to-es-1-0-1/16626/3 "2017-07-06T01:40:01Z")

</div>


