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

**URL:** <https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073>\
**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:** 1\
**Showing post:** 4

<div class="post-metadata">

**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")

</div>

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.

---

_[View the full topic](https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073)._