# Elastic Search 7 unable to bootstrap the cluster due to master not discovered yet **URL:** \ **Category:** Elasticsearch\ **Created:** [May 21, 2019, 5:36pm UTC](https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073 "2019-05-21T17:36:53Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Vishal\_Goel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishal_goel/32/46581_2.png) [@Vishal\_Goel](https://discuss.elastic.co/u/Vishal_Goel)\ **Post date:** [May 21, 2019, 5:36pm UTC](https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073/1 "2019-05-21T17:36:53Z")
Hi, 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 {10.254.43.206:9300}, bound_addresses {10.254.43.206:9300}, {172.18.48.177:9300}, {[fe80::1dc4:b009:43ef:5e17]:9300}, {192.168.1.28: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 [127.0.0.1:9300, 127.0.0.1:9301, 127.0.0.1:9302, 127.0.0.1:9303, 127.0.0.1:9304, [::1]:9300, [::1]:9301, [::1]:9302, [::1]:9303, [::1]:9304] from hosts providers and [{pc-vishalg}{rqf27K-JSv2FA4jKaZpe2g}{d3ykqL6oTSqg-AmkBvpIbQ}{pc-vishalg}{10.254.43.206:9300}{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. ---
**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\ **Post date:** [May 21, 2019, 8:11pm UTC](https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073/2 "2019-05-21T20:11:26Z")
Remove the port from the `cluster.initial_master_nodes` setting, and it will work 🙂 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. ---
**Author:** ![Vishal\_Goel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishal_goel/32/46581_2.png) [@Vishal\_Goel](https://discuss.elastic.co/u/Vishal_Goel)\ **Post date:** [May 22, 2019, 12:28am UTC](https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073/3 "2019-05-22T00:28:20Z")
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. ---
**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\ **Post date:** [May 22, 2019, 8:12am UTC](https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073/4 "2019-05-22T08:12:58Z")
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. ---
**Author:** ![Vishal\_Goel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishal_goel/32/46581_2.png) [@Vishal\_Goel](https://discuss.elastic.co/u/Vishal_Goel)\ **Post date:** [May 22, 2019, 8:59am UTC](https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073/5 "2019-05-22T08:59:52Z")
Ok. Got it. Thank you ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 19, 2019, 9:00am UTC](https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073/6 "2019-06-19T09:00:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.