Master node can not be elected After old master process got killed

Elastic Stack Elasticsearch
1

Here is my first configuration:

discovery.zen.minimum_master_nodes: 1

discovery.zen.ping.unicast.hosts:
[10.224.2.159,10.152.150.57,10.147.197.172,10.166.65.202]

If I kill master node ,The whole cluster is totally a mess.It doesn't elect
new master for the left 3 nodes
*
*
if query message,there is exception
"BroadcastShardOperationFailedException" in node 2 and node 3.node 1 and
node 4 is fine

Here is my second configuration:

discovery.zen.minimum_master_nodes: 4

discovery.zen.ping.unicast.hosts:
[10.224.2.159,10.152.150.57,10.147.197.172,10.166.65.202]

If I kill master node ,The whole cluster hang
*

there is no any information about cluster or nodes in bigdesk web
console , besides check "_cluster/health" return
"{"error":"MasterNotDiscoveredException[waited for [30s]]","status":503}"

So I assume ,If I give 4 IP address to "discovery.zen.ping.unicast.hosts:
"

All of this 4 IP can not leave this cluster,Otherwise the cluster will not
work properly

Am I right?

My Cluster is running on EC2 .How should I do to make Those nodes elect new
master If The old master dead?

Thanks
*

--
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

田晓亮 ,

Could you be missing the configuration item that disables multicast? (The
first in the 3 configuration items below.)

Here are the configuration items I used for a 3-node cluster using unicast
discovery and 2 masters required. The host names are changed but the basic
configuration should be easily understood:

discovery.zen.ping.multicast.enabled=false
discovery.zen.ping.unicast.hosts=host1,host2,host3
discovery.zen.minimum_master_nodes=2

Also, the largest index was configured with 2 replicas, so there exists one
copy of a shard on each node.

And note that a minimum of 2 masters is defined, but the entire cluster is
configured as 3 nodes (could be 4 if I had another server).

This cluster successfully surived a thermal shutdown of the third host. The
cluster state remained green with the first two hosts handling updates and
queries. When the third host was brought up, there were a few minutes where
the largest index (97M records across 5 shards) took some time to re-assign
/ re-verify the shards to the newly restored host. And now the cluster is
back in operation. Never missed a beat.

Hope this helps!

Regards,
Brian

On Monday, May 13, 2013 3:01:32 AM UTC-4, 田晓亮 wrote:

Here is my first configuration:

discovery.zen.minimum_master_nodes: 1

discovery.zen.ping.unicast.hosts:
[10.224.2.159,10.152.150.57,10.147.197.172,10.166.65.202]

If I kill master node ,The whole cluster is totally a mess.It doesn't
elect new master for the left 3 nodes
*
*
if query message,there is exception
"BroadcastShardOperationFailedException" in node 2 and node 3.node 1 and
node 4 is fine

Here is my second configuration:

discovery.zen.minimum_master_nodes: 4

discovery.zen.ping.unicast.hosts:
[10.224.2.159,10.152.150.57,10.147.197.172,10.166.65.202]

If I kill master node ,The whole cluster hang
*

there is no any information about cluster or nodes in bigdesk web
console , besides check "_cluster/health" return
"{"error":"MasterNotDiscoveredException[waited for [30s]]","status":503}"

So I assume ,If I give 4 IP address to "discovery.zen.ping.unicast.hosts:
"

All of this 4 IP can not leave this cluster,Otherwise the cluster will not
work properly

Am I right?

My Cluster is running on EC2 .How should I do to make Those nodes elect
new master If The old master dead?

Thanks
*

--
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

That really helps a lot,Thanks

2013/5/15 InquiringMind brian.from.fl@gmail.com

田晓亮 ,

Could you be missing the configuration item that disables multicast?
(The first in the 3 configuration items below.)

Here are the configuration items I used for a 3-node cluster using unicast
discovery and 2 masters required. The host names are changed but the basic
configuration should be easily understood:

discovery.zen.ping.multicast.enabled=false
discovery.zen.ping.unicast.hosts=host1,host2,host3
discovery.zen.minimum_master_nodes=2

Also, the largest index was configured with 2 replicas, so there exists
one copy of a shard on each node.

And note that a minimum of 2 masters is defined, but the entire cluster is
configured as 3 nodes (could be 4 if I had another server).

This cluster successfully surived a thermal shutdown of the third host.
The cluster state remained green with the first two hosts handling updates
and queries. When the third host was brought up, there were a few minutes
where the largest index (97M records across 5 shards) took some time to
re-assign / re-verify the shards to the newly restored host. And now the
cluster is back in operation. Never missed a beat.

Hope this helps!

Regards,
Brian

On Monday, May 13, 2013 3:01:32 AM UTC-4, 田晓亮 wrote:

Here is my first configuration:

discovery.zen.minimum_master_**nodes: 1

discovery.zen.ping.unicast.hosts: [10.224.2.159,10.152.150.57,
10.147.197.172,10.166.65.202]

If I kill master node ,The whole cluster is totally a mess.It doesn't
elect new master for the left 3 nodes
*
*
if query message,there is exception "BroadcastShardOperationFailedException"
in node 2 and node 3.node 1 and node 4 is fine

Here is my second configuration:

discovery.zen.minimum_master_**nodes: 4

discovery.zen.ping.unicast.hosts: [10.224.2.159,10.152.150.57,
10.147.197.172,10.166.65.202]

If I kill master node ,The whole cluster hang
*

there is no any information about cluster or nodes in bigdesk web
console , besides check "_cluster/health" return "{"error":"
MasterNotDiscoveredException[waited for [30s]]","status":503}"

So I assume ,If I give 4 IP address to "discovery.zen.ping.unicast.
hosts:
"

All of this 4 IP can not leave this cluster,Otherwise the cluster will
not work properly

Am I right?

My Cluster is running on EC2 .How should I do to make Those nodes elect
new master If The old master dead?

Thanks
*

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/FQ3KwTKy3r0/unsubscribe?hl=en-US
.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.