# Master Not Discovered (V: 6.1.0)

**URL:** <https://discuss.elastic.co/t/master-not-discovered-v-6-1-0/112938>\
**Category:** Elasticsearch\
**Created:** [December 22, 2017, 5:14am UTC](https://discuss.elastic.co/t/master-not-discovered-v-6-1-0/112938 "2017-12-22T05:14:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![shahamit2](https://avatars.discourse-cdn.com/v4/letter/s/9fc29f/32.png) [@shahamit2](https://discuss.elastic.co/u/shahamit2)\
**Post date:** [December 22, 2017, 5:14am UTC](https://discuss.elastic.co/t/master-not-discovered-v-6-1-0/112938/1 "2017-12-22T05:14:59Z")

</div>

ES version: 6.1.0  
It is 4 node cluster (2 master, 1 data and 1 client :: Minimum master is set to 2.)

Below is config of both master nodes.

* * *

```auto
cluster.name: infra_elasticsearch_wos_snapshot_us-west-2_cluster_7

# network settings
network.publish_host:
  - _local_
  - _ec2:privateDns_
  - _ec2:privateIp_

network.bind_host:
  - _local_
  - _ec2:privateDns_
  - _ec2:privateIp_

# http settings
http.max_content_length: 1000mb
http.cors.allow-origin: "/.*/"
http.cors.enabled: true
http.compression: true

# discovery settings
discovery.zen.hosts_provider: ec2
discovery.ec2.groups: infra_elasticsearch_wos_snapshot_us-west-2_cluster_7
discovery.ec2.any_group: false
discovery.zen.minimum_master_nodes: 2
discovery.zen.fd.ping_timeout: 60s
discovery.zen.fd.ping_retries: 3
cloud.node.auto_attributes: true

# allocation settings
cluster.routing.allocation.awareness.attributes: aws_availability_zone
cluster.routing.allocation.awareness.force.aws_availability_zone.values: us-west-2c,us-west-2b,us-west-2a

# roles
node.data: false
node.ingest: false
node.master: true
node.name: i-02d426454203be5bc

# other settings
bootstrap.memory_lock: true

```

===

Below is error observed in logfile.

```auto
[2017-12-22T04:58:46,272][WARN][o.e.d.z.ZenDiscovery] [i-02d426454203be5bc] not enough master nodes discovered during pinging (found [[Candidate{node={i-02d426454203be5bc}{iE5NE8PERFiitfE6ryKvdQ}{9FX6CuO5R6ercImJnUylzg}{ip-10-10-200-129.us-west-2.compute.internal}{10.10.200.129:9300}{aws_availability_zone=us-west-2c}, clusterStateVersion=-1}]], but needed [2]), pinging again
[2017-12-22T04:58:49,405][WARN][o.e.d.z.ZenDiscovery] [i-02d426454203be5bc] not enough master nodes discovered during pinging (found [[Candidate{node={i-02d426454203be5bc}{iE5NE8PERFiitfE6ryKvdQ}{9FX6CuO5R6ercImJnUylzg}{ip-10-10-200-129.us-west-2.compute.internal}{10.10.200.129:9300}{aws_availability_zone=us-west-2c}, clusterStateVersion=-1}]], but needed [2]), pinging again

```

Kindly help.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [December 22, 2017, 4:14pm UTC](https://discuss.elastic.co/t/master-not-discovered-v-6-1-0/112938/2 "2017-12-22T16:14:19Z")

</div>

You are using ec2 plugin, right?

You did not define the EC2 endpoint. Which means that it uses by default `ec2.us-east-1.amazonaws.com`.

I believe you need to fix that.

---

<div class="post-metadata">

**Author:** ![shahamit2](https://avatars.discourse-cdn.com/v4/letter/s/9fc29f/32.png) [@shahamit2](https://discuss.elastic.co/u/shahamit2)\
**Post date:** [December 26, 2017, 8:55am UTC](https://discuss.elastic.co/t/master-not-discovered-v-6-1-0/112938/3 "2017-12-26T08:55:52Z")

</div>

Thanks a ton David Pilato.  
Specifying EC2 endpoint helped.

Regards,  
Amit Shah.

---

<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 23, 2018, 8:56am UTC](https://discuss.elastic.co/t/master-not-discovered-v-6-1-0/112938/4 "2018-01-23T08:56:17Z")

</div>

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