# Elasticsearch throws 'not enough master nodes discovered during pinging' error

**URL:** <https://discuss.elastic.co/t/elasticsearch-throws-not-enough-master-nodes-discovered-during-pinging-error/146371>\
**Category:** Elasticsearch\
**Created:** [August 28, 2018, 2:25pm UTC](https://discuss.elastic.co/t/elasticsearch-throws-not-enough-master-nodes-discovered-during-pinging-error/146371 "2018-08-28T14:25:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![amruth](https://avatars.discourse-cdn.com/v4/letter/a/43a26b/32.png) [@amruth](https://discuss.elastic.co/u/amruth)\
**Post date:** [August 28, 2018, 2:25pm UTC](https://discuss.elastic.co/t/elasticsearch-throws-not-enough-master-nodes-discovered-during-pinging-error/146371/1 "2018-08-28T14:25:00Z")

</div>

Hi,

I am trying to setup Elasticsearch cluster(6.3.2) with 4 nodes(1 coordinating node and 3 Master Eligible and Data nodes). Elasticsearch is starting on all 4 nodes separately but it's not forming a cluster. Error I get is,

`not enough master nodes discovered during pinging`

Here are some setting in yml file,

```
node.master: true
node.data: true
bootstrap.memory_lock: true
network.host: 0.0.0.0
http.port: 9200
discovery.zen.ping.unicast.hosts: ["xxxxx", "xxxxx", "xxxxx"]
discovery.zen.minimum_master_nodes: 2

```

With exact same yml I've been running Production cluster(5.6.7) for long time  
I tried changing network.host to the exact ip address of the machine with no luck.

Can someone please help me understand the issue?

---

<div class="post-metadata">

**Author:** ![loren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/loren/32/44942_2.png) [@loren](https://discuss.elastic.co/u/loren)\
**Post date:** [August 28, 2018, 3:54pm UTC](https://discuss.elastic.co/t/elasticsearch-throws-not-enough-master-nodes-discovered-during-pinging-error/146371/2 "2018-08-28T15:54:12Z")

</div>

Every time this happens to me it's because whatever I am putting in for `"xxxxx"` is either

1. not matching up with the IP:port that other ES nodes are actually listening on (verify with `netstat`), or
2. that IP:port is just not reachable (verify with `curl`)

---

<div class="post-metadata">

**Author:** ![amruth](https://avatars.discourse-cdn.com/v4/letter/a/43a26b/32.png) [@amruth](https://discuss.elastic.co/u/amruth)\
**Post date:** [August 28, 2018, 8:22pm UTC](https://discuss.elastic.co/t/elasticsearch-throws-not-enough-master-nodes-discovered-during-pinging-error/146371/3 "2018-08-28T20:22:20Z")

</div>

> [@loren](#):
>
> not matching up with the IP:port that other ES nodes are actually listening on (verify with `netstat` ), or

Can you please explain how to check this?

> [@loren](#):
>
> that IP:port is just not reachable (verify with `curl` )

I've tested it with curl [http://xxxx:9200](http://xxxx:9200) and it gave me cluster information without any error (where xxxx is other machine's IP)

---

<div class="post-metadata">

**Author:** ![amruth](https://avatars.discourse-cdn.com/v4/letter/a/43a26b/32.png) [@amruth](https://discuss.elastic.co/u/amruth)\
**Post date:** [September 6, 2018, 3:16pm UTC](https://discuss.elastic.co/t/elasticsearch-throws-not-enough-master-nodes-discovered-during-pinging-error/146371/4 "2018-09-06T15:16:33Z")

</div>

Hi,

Can someone please help me on this?

Thanks in advance

---

<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:** [October 4, 2018, 3:16pm UTC](https://discuss.elastic.co/t/elasticsearch-throws-not-enough-master-nodes-discovered-during-pinging-error/146371/5 "2018-10-04T15:16:36Z")

</div>

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