Elasticsearch Unicast Weird Behavior in Clustering

I have two nodes each of which forms a cluster (with one empty node).

0.0.0.0:9200 (elasticsearch)
0.0.0.0:9201 (test-1)


Node at 9200 is in cluster elasticsearch (maybe default cluster.name). Node at 9201 is in cluster test-1. (Additionally, important or not, I bind network.hosts of both nodes to 0.0.0.0)

elasticsearch

cluster.name

test-1

network.host

I want to join a new node to test-1. When I leave discovery.zen.ping.unicast.hosts setting commented out alone, the new node is successfully joined to test-1. However, When I set it something else, e.g., ["0.0.0.0"] or ["127.0.1"], it is failed to join...

test-1

discovery.zen.ping.unicast.hosts

test-1

["0.0.0.0"]

["127.0.1"]

Joining a new node to elasticsearch has no problem. ["0.0.0.0"], ["127.0.1"] and ["IP"] all worked well. (But ["0.0.0.0", "ANOTHER-IP"] failed... Please answer about this as well if possible...)

elasticsearch

["0.0.0.0"]

["127.0.1"]

["IP"]

["0.0.0.0", "ANOTHER-IP"]

What causes this joining issue? Have anybody experienced problems like this?

1 Answer
1

The discovery.zen.ping.unicast.hosts should have the IPs of all the nodes joining the cluster. Do this for all the nodes in the cluster and use IPs not 0.0.0.0 or 127.0.0.1.

discovery.zen.ping.unicast.hosts

As your new node is trying to join the test-1 cluster you can try to change the port of the new node to 9201 and see if it joins.

test-1

The minimal things required to form a cluster:

cluster.name

node.name

discovery.zen.ping.unicast.hosts

gateway.recover_after_nodes and discovery.zen.minimum_master_nodes - comment these lines if they are not already so for all the nodes of the cluster.

gateway.recover_after_nodes

discovery.zen.minimum_master_nodes

Lastly check your firewall settings and disable the firewall if necessary. Check if the nodes can talk to each other.

2.

Thanks for contributing an answer to Stack Overflow!

But avoid …

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

But avoid …

To learn more, see our tips on writing great answers.

Required, but never shown

Required, but never shown

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.