# Frequent young GC loop crashing nodes

**URL:** <https://discuss.elastic.co/t/frequent-young-gc-loop-crashing-nodes/208955>\
**Category:** Elasticsearch\
**Created:** [November 21, 2019, 5:58pm UTC](https://discuss.elastic.co/t/frequent-young-gc-loop-crashing-nodes/208955 "2019-11-21T17:58:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![adam.wight](https://avatars.discourse-cdn.com/v4/letter/a/71e660/32.png) [@adam.wight](https://discuss.elastic.co/u/adam.wight)\
**Post date:** [November 21, 2019, 5:58pm UTC](https://discuss.elastic.co/t/frequent-young-gc-loop-crashing-nodes/208955/1 "2019-11-21T17:58:30Z")

</div>

Running ES 6.8.4 on a cluster with heavy search activity, for the past few weeks we're seeing nodes go into a continuous garbage collection loop, and eventually crash the ES process.

Is triggered by spike in search activity (from \< 100/s to 2000/s). Issue has occurred on each data node of 4 in cluster (also has 2x dedicated coordinating and 3x dedicated master nodes).  
Cluster has \< 100GB data in primary shards, in 8 indices (90% of that in 2 most heavily searched)

Data nodes did have 31GB heap, of 64GB total. Reduced to 16GB heap to test & issue remains.  
Ubuntu 18.04.03 VMs (hyper-v). Timing does coincide with recent increase to 24 core & reducing that back is next thing we'll test, but hard to understand how that might be related.

JVM has been upgraded to 1.8.0\_222, OS upgraded, and one of the nodes fully rebuilt to test & issue remains.

Any advice on next steps for troubleshooting/resolving?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/6/e650b35033baa8c275fecd09041aeaff507e8cf3.png)

---

<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 19, 2019, 5:58pm UTC](https://discuss.elastic.co/t/frequent-young-gc-loop-crashing-nodes/208955/2 "2019-12-19T17:58:33Z")

</div>

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