Hi Team,
I am new in elasticsearch and trying to add new node on cluster getting this error. Please Help.
[WARN ][o.e.c.c.ClusterFormationFailureHelper] [Elastic-2] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [faraz, Elastic-2] to bootstrap a cluster: have discovered [{Elastic-2}{jUg-b98CQEuPMwi9729ICg}{LE-NV4TaSTik5U4oBP8T0A}{localhost}{127.0.0.1:9300}{dilmrt}{
Welcome to our community! 
Please provide the config changes you made to Elasticsearch.
Thanks for the reply
Node name: Faraz
network.host: 192.168.3.181
transport.host: localhostdiscovery.seed_hosts: ["faraz", "Elastic-2"]
cluster.initial_master_nodes: ["faraz", "Elastic-2"]
node.data: true
node.master: true
bootstrap.memory_lock: false
Node Name; Elastic-2
xpack.security.enabled: false
xpack.security.transport.ssl.enabled: false
network.bind_host: 192.168.3.237
network.publish_host: 192.168.3.237
transport.host: localhost
discovery.seed_hosts: ["faraz:9200","Elastic-2:9200"]
node.master: true
node.data: true
cluster.initial_master_nodes: ["faraz","Elastic-2"]
One more error.
] [Elastic-2] received HTTP response on transport port, ensure that transport port (not HTTP port) of a remote node is specified in the configuration, [Netty4TcpChannel{localAddress=/192.168.3.237:54816, remoteAddress=Elastic-2/192.168.3.237:9200}], closing connection
You need to change 9200 to 9300, as per the second error.
I have changed and error 2 gone.
[WARN ][o.e.c.c.ClusterFormationFailureHelper] [Elastic-2] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [faraz, Elastic-2] to bootstrap a cluster: have discovered [{Elastic-2}{jUg-b98CQEuPMwi9729ICg}{ovyab5N4Si2AwmRLBIeonQ}{localhost}{127.0.0.1:9300}{dilmrt}{ml.machine_memory=1799823360, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}]; discovery will continue using [192.168.3.181:9300, 192.168.3.237:9300] from hosts providers and [{Elastic-2}{jUg-b98CQEuPMwi9729ICg}{ovyab5N4Si2AwmRLBIeonQ}{localhost}{127.0.0.1:9300}{dilmrt}{ml.machine_memory=1799823360, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
Dear Team,
Please help.
Hi,
Same subject today in the forum
https://discuss.elastic.co/t/3-node-cluster-failure/244533/3
Totally remove port number in discovery.seed_hosts was the solution.
Dominique
Hi,
I tried but unfortunately didn't worked.
Same error.
WARN ][o.e.c.c.ClusterFormationFailureHelper] [Elastic-2] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [faraz, Elastic-2] to bootstrap a cluster: have discovered [{Elastic-2}{jUg-b98CQEuPMwi9729ICg}{qHJE1aXQRjGkz18S8w_ojg}{localhost}{127.0.0.1:9300}{dilmrt}{ml.machine_memory=1799823360, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}]; discovery will continue using [192.168.3.181:9300, 192.168.3.237:9300] from hosts providers and [{Elastic-2}{jUg-b98CQEuPMwi9729ICg}{qHJE1aXQRjGkz18S8w_ojg}{localhost}{127.0.0.1:9300}{dilmrt}{ml.machine_memory=1799823360, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
Why is the node name Faraz when you specify faraz in the config?
Thanks for reply.
I changed it but same error.
What does the current config look like? What is the current error message?
Same error.
[WARN ][o.e.c.c.ClusterFormationFailureHelper] [Elastic-2] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [Faraz, Elastic-2] to bootstrap a cluster: have discovered [{Elastic-2}{jUg-b98CQEuPMwi9729ICg}{I_nZPCkcRDybaHYLZFpbuA}{localhost}{127.0.0.1:9300}{dilmrt}{ml.machine_memory=1799823360, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}]; discovery will continue using [192.168.3.181:9300, 192.168.3.237:9300] from hosts providers and [{Elastic-2}{jUg-b98CQEuPMwi9729ICg}{I_nZPCkcRDybaHYLZFpbuA}{localhost}{127.0.0.1:9300}{dilmrt}{ml.machine_memory=1799823360, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
Node Name : Faraz
discovery.seed_hosts: ["Faraz", "Elastic-2"]
cluster.initial_master_nodes: ["Faraz", "Elastic-2"]
node.data: true
node.master: true
bootstrap.memory_lock: true
Node Name: Elastic-2
discovery.seed_hosts: ["Faraz","Elastic-2"]
node.master: true
node.data: true
bootstrap.memory_lock: true
cluster.initial_master_nodes: ["Faraz","Elastic-2"]
Are these the actual host names? Can you connect using curl http://Faraz:9200 from the Elastic-2 node and vice versa? Is port 9300 accessible?
curl http://Elastic-2:9200
curl: (7) Failed connect to Elastic-2:9200; No route to host
Seems like it might be an issue with network or hostnames?
I have reached my daily limit thay why I answer from different user.
I disable firewall now Curl is working now but error is same
curl http://Elastic-2:9200
{
"name" : "Elastic-2",
"cluster_name" : "clusterone",
"cluster_uuid" : " na ",
"version" : {
"number" : "7.8.0",
"build_flavor" : "default",
"build_type" : "tar",
"build_hash" : "757314695644ea9a1dc2fecd26d1a43856725e65",
"build_date" : "2020-06-14T19:35:50.234439Z",
"build_snapshot" : false,
"lucene_version" : "8.5.1",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
Try to telnet to port 9300 from both host to make sure that is reachable. You can also try to use up addresses for seed hosts to see if that makes a difference.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.