Master-Slave not detected

Elastic Stack Elasticsearch
1

Hi,

I have 2 nodes that are on the same cluster and are not recognizing one
another (both are becoming "new master" when node loaded).

What should I check to resolve the issue?

Thanks,

Ophir

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

Did you modify elasticsearch.yml file?
Check unicast section if you disabled multicast.

Check also your firewall rules and open if needed 9300 port on each node.

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 4 mars 2013 à 12:58, Ophir Michaeli ophirmichaeli@gmail.com a écrit :

Hi,

I have 2 nodes that are on the same cluster and are not recognizing one another (both are becoming "new master" when node loaded).
What should I check to resolve the issue?

Thanks,
Ophir

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

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

Hi,

I returned to default yml config and added an inbound rule for port 9300 on
both machine nodes, multicast is enabled (by default).

The issue remains.

Thanks,

Ophir

On Monday, March 4, 2013 1:58:49 PM UTC+2, Ophir Michaeli wrote:

Hi,

I have 2 nodes that are on the same cluster and are not recognizing one
another (both are becoming "new master" when node loaded).

What should I check to resolve the issue?

Thanks,

Ophir

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

4

I used unicast to solve the issue:

Master Node elasticsearch.yml file –

node.master: true

Slave Nodes elasticsearch.yml file –

node.master: false

discovery.zen.ping.multicast.enabled: false

discovery.zen.ping.unicast.hosts: ["46.165.209.139"]

(46.165.209.139 is the master's ip address )

On Monday, March 4, 2013 4:27:51 PM UTC+2, Ophir Michaeli wrote:

Hi,

I returned to default yml config and added an inbound rule for port 9300
on both machine nodes, multicast is enabled (by default).

The issue remains.

Thanks,

Ophir

On Monday, March 4, 2013 1:58:49 PM UTC+2, Ophir Michaeli wrote:

Hi,

I have 2 nodes that are on the same cluster and are not recognizing one
another (both are becoming "new master" when node loaded).

What should I check to resolve the issue?

Thanks,

Ophir

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