# One of our nodes is constantly leaving with "master not discovered yet"

**URL:** <https://discuss.elastic.co/t/one-of-our-nodes-is-constantly-leaving-with-master-not-discovered-yet/349031>\
**Category:** Elasticsearch\
**Created:** [December 11, 2023, 10:34am UTC](https://discuss.elastic.co/t/one-of-our-nodes-is-constantly-leaving-with-master-not-discovered-yet/349031 "2023-12-11T10:34:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![coudenysj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/coudenysj/32/23108_2.png) [@coudenysj](https://discuss.elastic.co/u/coudenysj)\
**Post date:** [December 11, 2023, 10:34am UTC](https://discuss.elastic.co/t/one-of-our-nodes-is-constantly-leaving-with-master-not-discovered-yet/349031/1 "2023-12-11T10:34:01Z")

</div>

We have a cluster with 33 nodes, and one server (always the same one) is leaving the cluster quite often.

After restarting the service, it joins immediately.

The exact error is:

```auto
[2023-12-11T11:23:29,293][WARN][o.e.c.c.ClusterFormationFailureHelper] [elkdataw004.local] master not discovered yet: have discovered 
[
    {elkdataw004.local}{Hnd7niaLSoaqh12r01d0IA}{9b8EpeP4Q26XySf2I_j2nw}{elkdataw004.local}{elkdataw004.local}{x.x.159.183:9300}{sw}{8.11.1}{7000099-8500003},
    {elkmaster001.local}{05RymCqYR4SFoOC_gbJKGw}{i2NwqbM1TquDij8smGVITg}{elkmaster001.local}{elkmaster001.local}{x.x.4.16:9300}{m}{8.11.1}{7000099-8500003},
    {elkmaster002.local}{g9UxGx0nQuWH67uxDH0cgg}{DJlBkixiR_e4Qx2Y65wnFg}{elkmaster002.local}{elkmaster002.local}{x.x.4.17:9300}{m}{8.11.1}{7000099-8500003},
    {elkmaster003.local}{leNGcTahQDCQyebBqhTlKg}{MdN5wr9rQ9q-8iu2gjJGHA}{elkmaster003.local}{elkmaster003.local}{x.x.4.18:9300}{m}{8.11.1}{7000099-8500003}
];
discovery will continue using [
    x.x.4.17:9300, x.x.4.16:9300, x.x.4.18:9300
] from hosts providers and [
    {elkmaster002.local}{g9UxGx0nQuWH67uxDH0cgg}{DJlBkixiR_e4Qx2Y65wnFg}{elkmaster002.local}{elkmaster002.local}{x.x.4.17:9300}{m}{8.11.1}{7000099-8500003},
    {elkmaster003.local}{leNGcTahQDCQyebBqhTlKg}{MdN5wr9rQ9q-8iu2gjJGHA}{elkmaster003.local}{elkmaster003.local}{x.x.4.18:9300}{m}{8.11.1}{7000099-8500003},
    {elkmaster001.local}{05RymCqYR4SFoOC_gbJKGw}{i2NwqbM1TquDij8smGVITg}{elkmaster001.local}{elkmaster001.local}{x.x.4.16:9300}{m}{8.11.1}{7000099-8500003}
] from last-known cluster state;
node term 507, last-accepted version 18108627 in term 507;
joining [
    {elkmaster003.local}{leNGcTahQDCQyebBqhTlKg}{MdN5wr9rQ9q-8iu2gjJGHA}{elkmaster003.local}{elkmaster003.local}{x.x.4.18:9300}{m}{8.11.1}{7000099-8500003}
] in term [507] has status [waiting for local cluster applier] after [1.3m/79816ms];
for troubleshooting guidance, see https://www.elastic.co/guide/en/elasticsearch/reference/8.11/discovery-troubleshooting.html

```

How can I resolve this issue?

---

<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:** [December 11, 2023, 10:58am UTC](https://discuss.elastic.co/t/one-of-our-nodes-is-constantly-leaving-with-master-not-discovered-yet/349031/2 "2023-12-11T10:58:22Z")

</div>

> [@coudenysj](#):
>
> ```auto
> for troubleshooting guidance, see https://www.elastic.co/guide/en/elasticsearch/reference/8.11/discovery-troubleshooting.html
> 
> ```

Did you try this?

---

<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:** [January 8, 2024, 10:58am UTC](https://discuss.elastic.co/t/one-of-our-nodes-is-constantly-leaving-with-master-not-discovered-yet/349031/3 "2024-01-08T10:58:50Z")

</div>

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