# Elected master node doesn't communicate with other master nodes within expected time

**URL:** <https://discuss.elastic.co/t/elected-master-node-doesnt-communicate-with-other-master-nodes-within-expected-time/231375>\
**Category:** Elasticsearch\
**Created:** [May 6, 2020, 3:45pm UTC](https://discuss.elastic.co/t/elected-master-node-doesnt-communicate-with-other-master-nodes-within-expected-time/231375 "2020-05-06T15:45:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rangerdanger](https://avatars.discourse-cdn.com/v4/letter/r/67e7ee/32.png) [@rangerdanger](https://discuss.elastic.co/u/rangerdanger)\
**Post date:** [May 6, 2020, 3:45pm UTC](https://discuss.elastic.co/t/elected-master-node-doesnt-communicate-with-other-master-nodes-within-expected-time/231375/1 "2020-05-06T15:45:42Z")

</div>

Describe the feature:

**Elasticsearch version** (bin/elasticsearch --version): 7.5.2

**OS version (uname -a if on a Unix-like system):** CentOs 7 - 3.10.0-1062.18.1.el7.x86\_64

**Description of the problem including expected versus actual behavior:** Elected master node doesn't communicate with other master nodes within expected time. This is causing the re-election process and cluster turning RED

This issue keeps happening randomly all during the day, we are not sure what is actually causing "Master Not Discovered or Elected Yet". We first noticed this after adding 3 new Data nodes to our setup.

Below is the current setup

|no. of nodes| type| allocated heap |vm ram |cores|

|-----|-----|-----|----|----|

|3 |master nodes| 8gb |16gb |4|

|12| data nodes |16gb| 32gb |10|

|1| ingest node |8gb |18gb |4|

|2 |coordination nodes |16gb |32gb |10|

current storage: 10tb

number of shards: 5000

 ![81135745-fe82d780-8f1e-11ea-8b5e-5e502f2c1004](https://us1.discourse-cdn.com/elastic/original/3X/c/5/c510d822fc4837e74d02fe4c2ae417968acd1f1e.png)

---

<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:** [May 6, 2020, 6:13pm UTC](https://discuss.elastic.co/t/elected-master-node-doesnt-communicate-with-other-master-nodes-within-expected-time/231375/2 "2020-05-06T18:13:07Z")

</div>

Are you seeing any indication of long GC on the master nodes?

---

<div class="post-metadata">

**Author:** ![rangerdanger](https://avatars.discourse-cdn.com/v4/letter/r/67e7ee/32.png) [@rangerdanger](https://discuss.elastic.co/u/rangerdanger)\
**Post date:** [May 6, 2020, 6:40pm UTC](https://discuss.elastic.co/t/elected-master-node-doesnt-communicate-with-other-master-nodes-within-expected-time/231375/3 "2020-05-06T18:40:04Z")

</div>

We've been struggling with this issue for ~6 days and we definitely have seen gc of 1-4 seconds right before a crash but here are the most recent gc stats over the past 24 hours (none seem unusually long). During this timeframe we've seen ~3-4 blips/unstable moments for our cluster.

GC stats for the Active Master Node

 ![Screen Shot 2020-05-06 at 1.35.26 PM](https://us1.discourse-cdn.com/elastic/original/3X/2/2/22b2d535bf8640c22537ec7d8df1140768cb033d.jpeg)

---

<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:** [June 3, 2020, 6:40pm UTC](https://discuss.elastic.co/t/elected-master-node-doesnt-communicate-with-other-master-nodes-within-expected-time/231375/4 "2020-06-03T18:40:10Z")

</div>

Closed on June 3, 2020, 6:40pm UTC

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