# Master not discovered or elected yet

**URL:** <https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/318706>\
**Category:** Elasticsearch\
**Created:** [November 11, 2022, 6:02am UTC](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/318706 "2022-11-11T06:02:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![usilva](https://avatars.discourse-cdn.com/v4/letter/u/9f8e36/32.png) [@usilva](https://discuss.elastic.co/u/usilva)\
**Post date:** [November 11, 2022, 6:02am UTC](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/318706/1 "2022-11-11T06:02:58Z")

</div>

```auto
{"type": "server", "timestamp": "2022-11-11T05:46:01,375Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", 
"cluster.name": "elasticsearch", "node.name": "elasticsearch-master-0", "message": 
"master not discovered or elected yet, an election requires at least 2 nodes with ids from 
[V5J76_9wTUiXnn_qDuKsMw, PH593s2CQDyFouyI_7RXPA, PufPpGLoSlSMUHNws8gFVA], 
have only discovered non-quorum [{elasticsearch-master-0}{V5J76_9wTUiXnn_qDuKsMw}
{Pd_QEzMfSaapFoa3H-V-tA}{172.16.180.21}{172.16.180.21:9300}{cdfhilmrstw}]; 
discovery will continue using [] from hosts providers and 
[{elasticsearch-master-0}{V5J76_9wTUiXnn_qDuKsMw}{Pd_QEzMfSaapFoa3H-V-tA}
{172.16.180.21}{172.16.180.21:9300}{cdfhilmrstw}] 
from last-known cluster state; node term 856, last-accepted version 5425 in term 27" }

```

---

<div class="post-metadata">

**Author:** ![DineshNaik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dineshnaik/32/89308_2.png) [@DineshNaik](https://discuss.elastic.co/u/DineshNaik)\
**Post date:** [November 11, 2022, 8:11am UTC](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/318706/2 "2022-11-11T08:11:59Z")

</div>

Welcome to the community @usilva  
This is a very common error during initial setup and has been asked multiple times in the forum.  
please do search for this error and you will get references/ideas on how to fix this.

---

<div class="post-metadata">

**Author:** ![usilva](https://avatars.discourse-cdn.com/v4/letter/u/9f8e36/32.png) [@usilva](https://discuss.elastic.co/u/usilva)\
**Post date:** [November 11, 2022, 9:07am UTC](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/318706/3 "2022-11-11T09:07:40Z")

</div>

@DineshNaik Thanks for the reply. The thing is my one is somewhat different scenario

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 11, 2022, 9:12am UTC](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/318706/4 "2022-11-11T09:12:46Z")

</div>

Since you have not provided any details of your setup apart from a single error message that is impossible to tell. If you want to get help you will most likely need to provide a lot more context around your cluster and the issue.

---

<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:** [December 9, 2022, 9:12am UTC](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/318706/5 "2022-12-09T09:12:52Z")

</div>

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