The node on server ***1 has master and data roles. The node on server ***2 has data role. I started ES instances on both servers without errors in their log files. Also, I can successfully request indices via curl on server ***1.
Unfortunately data node on server ***2 is not joining the cluster and running check for its health with curl -XGET 'http://***2:9201/_cat/health?v' on the server ***2 console outputs the following error: ("error":("root_cause":[("type":"master_not_discovered_exception","reason":"null"), "status":503)
I think I might be missing something in config files, may be on the transport level or something else and any advise or help to resolve the issue will be appreciated.
I commented out the network.host in es yml on both servers, then started es on first server but it failed to start, the entries in log file: [INFO][o.e.b.BootstrapChecks] [es-node1] bound or publishing to a non-loopback or non-link-local address, enforsing bootstrap checks [ERROR][o.e.b.Bootstrap][es-node1] node validation exception bootstrap checks failed ... ...stopped ...closed
You should do settings for network host only. no need to mention transport host and port parameter and also for discovery.unicast parameter mention only with Ips. Also make sure the entries for both server in its host file for better communication between servers . Also open port 9200 and 9300 on both servers.
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext