Zen Discovery cannot resolve the master

Elastic Stack Elasticsearch
1

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.
For more options, visit https://groups.google.com/groups/opt_out.

2

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.
For more options, visit https://groups.google.com/groups/opt_out.

3

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
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 29 avr. 2013 à 11:30, Sicker 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.
For more options, visit https://groups.google.com/groups/opt_out.

<tropicsearch01.log2013-04-27><tropicsearch02.log2013-04-27><tropicsearch03.log2013-04-27><tropicsearch04.log2013-04-27>