# Discovery configuration changes in 7.x

**URL:** <https://discuss.elastic.co/t/discovery-configuration-changes-in-7-x/260522>\
**Category:** Elasticsearch\
**Created:** [January 8, 2021, 9:41am UTC](https://discuss.elastic.co/t/discovery-configuration-changes-in-7-x/260522 "2021-01-08T09:41:14Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![srikanth\_k](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@srikanth\_k](https://discuss.elastic.co/u/srikanth_k)\
**Post date:** [January 8, 2021, 9:41am UTC](https://discuss.elastic.co/t/discovery-configuration-changes-in-7-x/260522/1 "2021-01-08T09:41:14Z")

</div>

Before an upgrade to 7.x, why is it required to set the below value  
`discovery.zen.ping.unicast.hosts` ?

_" After the cluster forms successfully for the first time, remove the `cluster.initial_master_nodes` setting from each nodes' configuration. Do not use this setting when restarting a cluster or adding a new node to an existing cluster."_

Does this setting needs to be explicitly removed from elasticsearch.yml file after cluster bootstrapping is completed?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [January 8, 2021, 11:07am UTC](https://discuss.elastic.co/t/discovery-configuration-changes-in-7-x/260522/2 "2021-01-08T11:07:24Z")

</div>

Yes you should remove `cluster.initial_master_nodes` from your config file once the cluster has formed for the first time.

You should not use `discovery.zen.ping.unicast.hosts` at all in 7.x, instead use `discovery.seed_hosts`, and don't remove this from your config file.

---

<div class="post-metadata">

**Author:** ![srikanth\_k](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@srikanth\_k](https://discuss.elastic.co/u/srikanth_k)\
**Post date:** [January 12, 2021, 5:48am UTC](https://discuss.elastic.co/t/discovery-configuration-changes-in-7-x/260522/3 "2021-01-12T05:48:35Z")

</div>

Thanks for the reply.  
I think my first question is not clear. let me rephrase it.  
**Before an upgrade to 7.x, In the documentation i see its mentioned that we need to set the below value `discovery.zen.ping.unicast.hosts`**  
So i infer that we need to set this value in 6.x before i upgrade to 7.x.  
Why is this required?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [January 12, 2021, 6:24am UTC](https://discuss.elastic.co/t/discovery-configuration-changes-in-7-x/260522/4 "2021-01-12T06:24:49Z")

</div>

The documentation you quoted does not mention `discovery.zen.ping.unicast.hosts`.

---

<div class="post-metadata">

**Author:** ![srikanth\_k](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@srikanth\_k](https://discuss.elastic.co/u/srikanth_k)\
**Post date:** [January 13, 2021, 7:45am UTC](https://discuss.elastic.co/t/discovery-configuration-changes-in-7-x/260522/5 "2021-01-13T07:45:28Z")

</div>

> **[Breaking changes in 7.0 | Elasticsearch Reference \[7.10\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes-7.0.html#_discovery_configuration_is_required_in_production)**

_" The first three settings in this list are only available in versions 7.0 and above. If you are preparing to upgrade from an earlier version, you must set `discovery.zen.ping.unicast.hosts` or `discovery.zen.hosts_provider` ."_

we need to set this value in 6.x before i upgrade to 7.x.  
Why is this required?

---

<div class="post-metadata">

**Author:** ![Rajath\_H\_G](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rajath_h_g/32/81933_2.png) [@Rajath\_H\_G](https://discuss.elastic.co/u/Rajath_H_G)\
**Post date:** [January 13, 2021, 8:02am UTC](https://discuss.elastic.co/t/discovery-configuration-changes-in-7-x/260522/6 "2021-01-13T08:02:50Z")

</div>

Hi David,

What happens if we keep the setting "cluster.initial\_master\_nodes" even after cluster formation ?

And i think what Srikanth was asking is, does it really necessary to set "discovery.zen.ping.unicast.hosts" to list of master eligible nodes on all the nodes in 6.8 (6.x) cluster before upgrading to 7.x ?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [January 13, 2021, 9:33am UTC](https://discuss.elastic.co/t/discovery-configuration-changes-in-7-x/260522/7 "2021-01-13T09:33:18Z")

</div>

> [@Rajath\_H\_G](#):
>
> What happens if we keep the setting "cluster.initial\_master\_nodes" even after cluster formation ?

There's a risk that you accidentally bootstrap a second cluster in the future, which would be bad because you can't merge clusters together.

> [@Rajath\_H\_G](#):
>
> does it really necessary to set "discovery.zen.ping.unicast.hosts" to list of master eligible nodes on all the nodes in 6.8 (6.x) cluster before upgrading to 7.x ?

You would normally set `discovery.zen.ping.unicast.hosts` to the addresses of the master-eligible nodes in 6.8 anyway?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 10, 2021, 9:33am UTC](https://discuss.elastic.co/t/discovery-configuration-changes-in-7-x/260522/8 "2021-02-10T09:33:24Z")

</div>

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