# Crashing Suspect Garbage Compiler

**URL:** <https://discuss.elastic.co/t/crashing-suspect-garbage-compiler/149300>\
**Category:** Elasticsearch\
**Created:** [September 20, 2018, 1:32pm UTC](https://discuss.elastic.co/t/crashing-suspect-garbage-compiler/149300 "2018-09-20T13:32:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kurtiskurtis](https://avatars.discourse-cdn.com/v4/letter/k/45deac/32.png) [@kurtiskurtis](https://discuss.elastic.co/u/kurtiskurtis)\
**Post date:** [September 20, 2018, 1:32pm UTC](https://discuss.elastic.co/t/crashing-suspect-garbage-compiler/149300/1 "2018-09-20T13:32:19Z")

</div>

Every few days, my cluster gets into a bad state where a few of the nodes are disconnected (seems like the master removes them).

Right at the same time they are removed, the node shows this in their logs:

```
[2018-09-20T08:25:14,454][WARN][o.e.m.j.JvmGcMonitorService] [es-data-8] [gc][old][208889][624] duration [1.3m], collections [1]/[1.3m], total [1.3m]/[29.1m], memory [23.9gb]->[24gb]/[24.9gb], all_pools {[young] [55mb]->[60.1mb]/[532.5mb]}{[survivor] [0b]->[0b]/[66.5mb]}{[ol$

```

If my understanding is correct a 1.3m duration is way too long. Typically these logs show \<1 second but every few days they start getting into the minutes long and then everything comes collapsing down.

---

<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 18, 2018, 1:40pm UTC](https://discuss.elastic.co/t/crashing-suspect-garbage-compiler/149300/2 "2018-10-18T13:40:53Z")

</div>

Closed on October 18, 2018, 1:40pm UTC

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