# Zen Discovery cannot resolve the master

**URL:** https://discuss.elastic.co/t/zen-discovery-cannot-resolve-the-master/11728
**Category:** Elasticsearch
**Created:** [April 29, 2013, 9:30am UTC](https://discuss.elastic.co/t/zen-discovery-cannot-resolve-the-master/11728 "2013-04-29T09:30:40Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Sicker](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@Sicker](https://discuss.elastic.co/u/Sicker)
#### Post date: [April 29, 2013, 9:30am UTC](https://discuss.elastic.co/t/zen-discovery-cannot-resolve-the-master/11728/1 "2013-04-29T09:30:40Z")

</div>

I use ES 0.19.1and use discovery.zen.minimum\_master\_nodes: 2, and restart  
as this timeline

Time

Node1

Node2

Node3

Node4

- 

Up(Master)

Up

Up

Up

2013-04-27 15:21:27

(Shutdown)

Up(Master)

2013-04-27 15:21:39

Up

2013-04-27 15:22:06

(Shutdown)

Up(Master)

2013-04-27 15:22:25

(Shutdown)

Up (Master)

_2013-04-27 15:22:41_

(Shutdown)

_2013-04-27 15:22:41_

Up

2013-04-27 15:23.10

Up

2013-04-27 15:23.18

Up

After this every node cannot join the cluster. What happened in this case?

--  
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).  
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: [April 29, 2013, 9:56am UTC](https://discuss.elastic.co/t/zen-discovery-cannot-resolve-the-master/11728/2 "2013-04-29T09:56:26Z")

</div>

It seems you play bingo with Elasticsearch.

Watch for the shard relocation after you shutdown a node. If relocations  
for indexes are in progress, these indexes are not available on that  
node and the node state is not ready. You must ensure a node is started  
and active and ready for master election.

Jörg

Am 29.04.13 11:30, schrieb Sicker:

> I use ES 0.19.1and use discovery.zen.minimum\_master\_nodes: 2, and  
> restart as this timeline
> 
> Time
> 
> Node1
> 
> Node2
> 
> Node3
> 
> Node4
> 
> - 
> 
> Up(Master)
> 
> Up
> 
> Up
> 
> Up
> 
> 2013-04-27 15:21:27
> 
> (Shutdown)
> 
> Up(Master)
> 
> 2013-04-27 15:21:39
> 
> Up
> 
> 2013-04-27 15:22:06
> 
> (Shutdown)
> 
> Up(Master)
> 
> 2013-04-27 15:22:25
> 
> (Shutdown)
> 
> Up (Master)
> 
> _2013-04-27 15:22:41_
> 
> (Shutdown)
> 
> _2013-04-27 15:22:41_
> 
> Up
> 
> 2013-04-27 15:23.10
> 
> Up
> 
> 2013-04-27 15:23.18
> 
> Up
> 
> After this every node cannot join the cluster. What happened in this case?

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [April 29, 2013, 10:41am UTC](https://discuss.elastic.co/t/zen-discovery-cannot-resolve-the-master/11728/3 "2013-04-29T10:41:06Z")

</div>

Can you update to at least latest elasticsearch 0.19.12? 0.19.1 is very very old (more than a year).  
Also, consider moving to 0.20.6.

I remember that some issues about discovery have been fixed in the last year. May be it could help here.

My 2 cents

--  
David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)  
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 29 avr. 2013 à 11:30, Sicker [sicker27@gmail.com](mailto:sicker27@gmail.com) a écrit :

> I use ES 0.19.1and use discovery.zen.minimum\_master\_nodes: 2, and restart as this timeline
> 
> Time
> 
> Node1
> 
> Node2
> 
> Node3
> 
> Node4
> 
> - 
> 
> Up(Master)
> 
> Up
> 
> Up
> 
> Up
> 
> 2013-04-27 15:21:27
> 
> (Shutdown)
> 
> Up(Master)
> 
> 2013-04-27 15:21:39
> 
> Up
> 
> 2013-04-27 15:22:06
> 
> (Shutdown)
> 
> Up(Master)
> 
> 2013-04-27 15:22:25
> 
> (Shutdown)
> 
> Up (Master)
> 
> 2013-04-27 15:22:41
> 
> (Shutdown)
> 
> 2013-04-27 15:22:41
> 
> Up
> 
> 2013-04-27 15:23.10
> 
> Up
> 
> 2013-04-27 15:23.18
> 
> Up
> 
> After this every node cannot join the cluster. What happened in this case?
> 
> --  
> 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).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> \<tropicsearch01.log2013-04-27\>\<tropicsearch02.log2013-04-27\>\<tropicsearch03.log2013-04-27\>\<tropicsearch04.log2013-04-27\>

---

<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:39am UTC](https://discuss.elastic.co/t/zen-discovery-cannot-resolve-the-master/11728/4 "2017-07-06T02:39:15Z")

</div>


