Elastic Search 7 unable to bootstrap the cluster due to master not discovered yet


I downloaded ES 7 zip package on Windows 10. I am running elasticsearch.bat simply by just double clicking it to start my first node (master) of the cluster. I am getting following error on warning (not able to bootstrap the cluster):

[2019-05-21T22:55:58,108][INFO ][o.e.n.Node               ] [pc-vishalg] node name [pc-vishalg], node ID [rqf27K-JSv2FA4jKaZpe2g], cluster name [elasticsearch]
[2019-05-21T22:56:24,406][INFO ][o.e.t.TransportService   ] [pc-vishalg] publish_address {}, bound_addresses {}, {}, {[fe80::1dc4:b009:43ef:5e17]:9300}, {}, {[fe80::4e16:7aba:42dc:7b2a]:9300}, {[fe80::216e:d23c:95b8:b711]:9300}, {[fe80::16:3529:f222:ee0e]:9300}
[2019-05-21T22:56:24,428][INFO ][o.e.b.BootstrapChecks    ] [pc-vishalg] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2019-05-21T22:56:24,459][INFO ][o.e.c.c.ClusterBootstrapService] [pc-vishalg] skipping cluster bootstrapping as local node does not match bootstrap requirements: [pc-vishalg:9300]
**[2019-05-21T22:56:34,472][WARN ][o.e.c.c.ClusterFormationFailureHelper] [pc-vishalg] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [pc-vishalg:9300] to bootstrap a cluster: have discovered []; discovery will continue using [,,,,, [::1]:9300, [::1]:9301, [::1]:9302, [::1]:9303, [::1]:9304] from hosts providers and [{pc-vishalg}{rqf27K-JSv2FA4jKaZpe2g}{d3ykqL6oTSqg-AmkBvpIbQ}{pc-vishalg}{}{ml.machine_memory=17058791424, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0**

My elasticsearch.yml is as follows:

node.name: pc-vishalg
cluster.initial_master_nodes: ["pc-vishalg:9300"]
network.bind_host: pc-vishalg
network.publish_host: pc-vishalg

Acc. to the documentation, node.name should be same as initial_master_nodes which I did provide. Can you please help me why am I getting above warning. Is anything I am doing wrong.
One observation: if I use actual IP in initial_master_nodes (not in node.name) only, it works out, create the cluster and no warnings are seen.

Remove the port from the cluster.initial_master_nodes setting, and it will work :slight_smile: We have updated the docs recently to make it clearer that either node name, or ip/port is to be used. Node name/port is not a valid combination.

Thanks, I will give it a try. But, is it intentional or a bug?
What if I want to run masters ES on some random ports e.g. 5200. How it is going to work with only host name as part of master list.

It is intentional. This setting does not denote a hostname, but the node name or the advertised publish address. In particular, it is not an address that is resolved or actively connected to. The discovery.seed_hosts setting is used for that. The cluster.initial_master_nodes setting is used to determine the identities of the subset of master-eligible nodes that participate in the bootstrapping process after discovery.seed_hosts has established a connection to the nodes.

Ok. Got it. Thank you

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