Elastic search clustering error


(suresh) #1

cluster.name: Elk-cluster
node.name: node-2
node.master: true
node.data: true
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: 10.85.17.xxx
http.port: 9200
discovery.zen.ping.unicast.hosts: ["10.85.17.xxx", "10.85.17.xxx"]

Above is the elastic search yml file.
Error output below
failed to send join request to master [{node-2}{motkOcYTTTaa__gny7qTJg}{KXLB9hr0T9CH4T8ScbQuBQ}{10.85.17.221}{10.85.17.221:9300}], reason [RemoteTransportException[[node-2][10.85.17.221:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{node-2}{motkOcYTTTaa__gny7qTJg}{KXLB9hr0T9CH4T8ScbQuBQ}{10.85.17.221}{10.85.17.221:9300}] not master for join request]; ], tried [3] times


(Alexander Reelsen) #2

please take some more time to describe your setup. Two nodes? No lode balancing? No virtual IPs or anything?

What are the logs on the other node showing (the log message indicates this node is not a master node either, but there should be a reason why this is the case).


(suresh) #3

Thanks for writing!

Second server configuration
network.host: 10.85.17.221

transport.publish_port: 9300
http.port: 9200
discovery.zen.ping.unicast.hosts: ["10.85.17.220", "10.85.17.221"]
node.name: node-2
node.master: true
node.data: true
cluster.name: Elk-cluster
Error - output

[node-2] failed to send join request to master [{node-1}{motkOcYTTTaa__gny7qTJg}{bejYCDrRTkqYHK0I1FKtEQ}{10.85.17.220}{10.85.17.220:9300}], reason [RemoteTransportException[[node-1][10.85.17.220:9300][internal:discovery/zen/join]]; nested: NotMasterException[Node [{node-1}{motkOcYTTTaa__gny7qTJg}{bejYCDrRTkqYHK0I1FKtEQ}{10.85.17.220}{10.85.17.220:9300}] not master for join request]; ], tried [3] times


(Alexander Reelsen) #4

Please take the time to properly format your messages. You can use markdown here which has excellent support for code snippets.

the logs files from both nodes are still missing.


(system) #5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.