# Elasticsearch 1.5 cluster going to RED state due to some nodes constantly exiting and rejoining the cluster

**URL:** <https://discuss.elastic.co/t/elasticsearch-1-5-cluster-going-to-red-state-due-to-some-nodes-constantly-exiting-and-rejoining-the-cluster/40516>\
**Category:** Elasticsearch\
**Created:** [January 29, 2016, 7:20pm UTC](https://discuss.elastic.co/t/elasticsearch-1-5-cluster-going-to-red-state-due-to-some-nodes-constantly-exiting-and-rejoining-the-cluster/40516 "2016-01-29T19:20:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sarya](https://avatars.discourse-cdn.com/v4/letter/s/3ab097/32.png) [@sarya](https://discuss.elastic.co/u/sarya)\
**Post date:** [January 29, 2016, 7:20pm UTC](https://discuss.elastic.co/t/elasticsearch-1-5-cluster-going-to-red-state-due-to-some-nodes-constantly-exiting-and-rejoining-the-cluster/40516/1 "2016-01-29T19:20:05Z")

</div>

We have been noticing our elasticsearch cluster is often going to RED state and queries are timing out .  
We have noticed that some nodes have high JVM memory utilization and soon exiting the cluster ( from the logs we see out of memory errors on that node and it looks like the node cannot be reached by other cluster members / Master) .  
The node eventually recovers after several hours by itself but this is causing an application outage due to the timeout .  
We have set the property  
indices.fielddata.cache.size: 40%

as per elasticsearch recommendation which we thought would avoid this problem . However it doesn't seem to work .  
We also set  
ES\_MIN\_MEM: 15g  
ES\_MAX\_MEM: 15g  
on our machines which have 30 GB RAM .

Any help appreciated .  
Thanks

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 30, 2016, 1:19am UTC](https://discuss.elastic.co/t/elasticsearch-1-5-cluster-going-to-red-state-due-to-some-nodes-constantly-exiting-and-rejoining-the-cluster/40516/2 "2016-01-30T01:19:21Z")

</div>

Do you have Marvel installed? If not I would start there, it'll tell you what is happening with a bit more certainty.

---

<div class="post-metadata">

**Author:** ![sarya](https://avatars.discourse-cdn.com/v4/letter/s/3ab097/32.png) [@sarya](https://discuss.elastic.co/u/sarya)\
**Post date:** [February 1, 2016, 9:11pm UTC](https://discuss.elastic.co/t/elasticsearch-1-5-cluster-going-to-red-state-due-to-some-nodes-constantly-exiting-and-rejoining-the-cluster/40516/3 "2016-02-01T21:11:14Z")

</div>

Yes , we have marvel installed , but what should we specifically look for this particular issue .  
Thanks

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 2, 2016, 3:11am UTC](https://discuss.elastic.co/t/elasticsearch-1-5-cluster-going-to-red-state-due-to-some-nodes-constantly-exiting-and-rejoining-the-cluster/40516/4 "2016-02-02T03:11:06Z")

</div>

Heap use and GC, that's what it sounds like.

---

<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:** [July 5, 2017, 11:19pm UTC](https://discuss.elastic.co/t/elasticsearch-1-5-cluster-going-to-red-state-due-to-some-nodes-constantly-exiting-and-rejoining-the-cluster/40516/5 "2017-07-05T23:19:48Z")

</div>