# Master not discovered or elected yet

**URL:** <https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/206911>\
**Category:** Elasticsearch\
**Created:** [November 7, 2019, 7:19am UTC](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/206911 "2019-11-07T07:19:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![skills-anand](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skills-anand/32/57305_2.png) [@skills-anand](https://discuss.elastic.co/u/skills-anand)\
**Post date:** [November 7, 2019, 7:19am UTC](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/206911/1 "2019-11-07T07:19:35Z")

</div>

Hello,

I have a cluster with 4 nodes. Where node 1 is master and all other nodes i set master as false.

I tried to connect with 3 nodes properly when i start connecting with node 4 in same cluster i got the following error

master not discovered or elected yet, an election requires at least 2 nodes with ids (XXXX, yyyyyy)

```
[2019-11-07T06:45:33,425][TRACE][o.e.d.PeerFinder] [node-1] startProbe(XX.XX.XX.XX:9300) not probing local node[2019-11-07T06:45:33,426][TRACE][o.e.d.SeedHostsResolver] [node-1] resolved host [XX.XX.XX.XX] to [XX.XX.XX.XX:9300][2019-11-07T06:45:33,427][TRACE][o.e.d.PeerFinder] [node-1] probing resolved transport addresses [][2019-11-07T06:45:33,429][TRACE][o.e.d.PeerFinder] [node-1] Peer{transportAddress=YY.YY.YY.YY:9300, discoveryNode={node-2}{DWIcFNpVTveixJFv9HDl-Q}{Ckx6sPDIS6mSlNvDTaq36g}{YY.YY.YY.YY}{YY.YY.YY.YY:9300}{dilm}{ml.machine_memory=67275157504, ml.max_open_jobs=20, xpack.installed=true}, peersRequestInFlight=true} received PeersResponse{masterNode=Optional.empty, knownPeers=[{node-1}{0ke8pQgxT56nvrgBk4cgXg}{QwHgsNo4SYefBr9f0vi6Dw}{XX.XX.XX.XX}{XX.XX.XX.XX:9300}{dim}{ml.machine_memory=67275157504, ml.max_open_jobs=20, xpack.installed=true}], term=83}[2019-11-07T06:45:33,430][TRACE][o.e.d.PeerFinder] [node-1] startProbe(XX.XX.XX.XX:9300) not probing local node [2019-11-07T06:45:34,007][TRACE][o.e.d.PeerFinder] [node-1] startProbe(XX.XX.XX.XX:9300) not probing local node

```

[2019-11-07T06:45:34,158][TRACE][o.e.d.PeerFinder] [node-1] startProbe(XX.XX.XX.XX:9300) not probing local node [2019-11-07T06:45:34,426][TRACE][o.e.d.PeerFinder] [node-1] Peer{transportAddress=YY.YY.YY.YY:9300, discoveryNode={node-2}{DWIcFNpVTveixJFv9HDl-Q}{Ckx6sPDIS6mSlNvDTaq36g}{YY.YY.YY.YY}{YY.YY.YY.YY:9300}{dilm}{ml.machine\_memory=67275157504, ml.max\_open\_jobs=20, xpack.installed=true},

---

<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:** [November 7, 2019, 12:04pm UTC](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/206911/2 "2019-11-07T12:04:32Z")

</div>

> [@skills-anand](#):
>
> i got the following error
> 
> master not discovered or elected yet, an election requires at least 2 nodes with ids (XXXX, yyyyyy)

That's not the whole message, and the bit of the message you have deleted is usually the bit that explains the 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:** [November 7, 2019, 2:14pm UTC](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/206911/4 "2019-11-07T14:14:24Z")

</div>

That doesn't help. We need to see the rest of the message that starts `master not discovered or elected yet`.

---

<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 6, 2019, 6:09am UTC](https://discuss.elastic.co/t/master-not-discovered-or-elected-yet/206911/6 "2019-12-06T06:09:03Z")

</div>

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