# GC Collector Error shut down ingest node

**URL:** <https://discuss.elastic.co/t/gc-collector-error-shut-down-ingest-node/149115>\
**Category:** Elasticsearch\
**Created:** [September 19, 2018, 11:20am UTC](https://discuss.elastic.co/t/gc-collector-error-shut-down-ingest-node/149115 "2018-09-19T11:20:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Emiliano\_Baum](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emiliano_baum/32/5186_2.png) [@Emiliano\_Baum](https://discuss.elastic.co/u/Emiliano_Baum)\
**Post date:** [September 19, 2018, 11:20am UTC](https://discuss.elastic.co/t/gc-collector-error-shut-down-ingest-node/149115/1 "2018-09-19T11:20:20Z")

</div>

The elastic service shut down when the log report the following error.  
I use ES 5.6, over Ubuntu server 16.04. The cluster have 10 nodes, two of this are ingestion nodes, and one of this have the problem.  
this is the service log:

```
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: enabled)
   Active: failed (Result: signal) since Tue 2018-09-18 22:00:33 UTC; 13h ago

```

and this is the log of the application:

```
[2018-09-18T21:59:51,874][INFO][o.e.m.j.JvmGcMonitorService] [MON-CGSSESCluster01IngestNode2-S] [gc][117706] overhead, spent [313ms] collecting in the last [1s]
[2018-09-18T21:59:56,685][INFO][o.e.m.j.JvmGcMonitorService] [MON-CGSSESCluster01IngestNode2-S] [gc][young][117710][20382] duration [917ms], collections [1]/[1.7s], total [917ms]/[23.6m], memory [5.7gb]->[5.7gb]/[9.9gb], all_pools {[young] [288.4mb]->[43.3mb]/[532.5mb]}{[survivor] [66.5mb]->[66.5mb]/[66.5mb]}{[old] [5.4gb]->[5.5gb]/[9.3gb]}
[2018-09-18T21:59:56,688][WARN][o.e.m.j.JvmGcMonitorService] [MON-CGSSESCluster01IngestNode2-S] [gc][117710] overhead, spent [917ms] collecting in the last [1.7s]
[2018-09-18T22:00:00,836][INFO][o.e.m.j.JvmGcMonitorService] [MON-CGSSESCluster01IngestNode2-S] [gc][117714] overhead, spent [443ms] collecting in the last [1.1s]
```

---

<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:** [September 19, 2018, 9:24pm UTC](https://discuss.elastic.co/t/gc-collector-error-shut-down-ingest-node/149115/2 "2018-09-19T21:24:33Z")

</div>

Can you post most of the log, there's nothing there that suggests that the node was shutdown.

---

<div class="post-metadata">

**Author:** ![Emiliano\_Baum](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emiliano_baum/32/5186_2.png) [@Emiliano\_Baum](https://discuss.elastic.co/u/Emiliano_Baum)\
**Post date:** [September 20, 2018, 10:57am UTC](https://discuss.elastic.co/t/gc-collector-error-shut-down-ingest-node/149115/3 "2018-09-20T10:57:59Z")

</div>

> [@Emiliano\_Baum](#):
>
> ```auto
> 
> ```

Hi warkholm, the elastic log don't say to much, only the lines i pasted before. The service status said the proccess was killed at the same time the elastic log report the overhead warning.  
This error could be caused for a lot of querys to the node?

I have two dedicated ingestion nodes that mainly receive indexing messages. To monitor the cluster, I use "Cerebro", and I suspect that the problem is due to this software, because yesterday I lowered the refresh rate and until now the cluster does not report problems

---

<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, 10:58am UTC](https://discuss.elastic.co/t/gc-collector-error-shut-down-ingest-node/149115/4 "2018-10-18T10:58:00Z")

</div>

Closed on October 18, 2018, 10:58am UTC

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