# Elasticsearch coordinating node gc.log

**URL:** <https://discuss.elastic.co/t/elasticsearch-coordinating-node-gc-log/224994>\
**Category:** Elasticsearch\
**Created:** [March 25, 2020, 2:07pm UTC](https://discuss.elastic.co/t/elasticsearch-coordinating-node-gc-log/224994 "2020-03-25T14:07:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![andras.vecsi](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@andras.vecsi](https://discuss.elastic.co/u/andras.vecsi)\
**Post date:** [March 25, 2020, 2:07pm UTC](https://discuss.elastic.co/t/elasticsearch-coordinating-node-gc-log/224994/1 "2020-03-25T14:07:50Z")

</div>

Hi All,

I have a 3 node elasticsearch cluster.  
I'm connecting my Kibana to this cluster through elasticsearch coordinating node

The elasticsearch coordinating node and kibana is running on the same server.

For my coordinating node I can see every minute:

> ```
> [2020-03-25T13:56:25.342+0000][20967][gc,start] GC(0) Pause Young (Allocation Failure)
> [2020-03-25T13:56:25.343+0000][20967][gc,task] GC(0) Using 4 workers of 4 for evacuation
> [2020-03-25T13:56:25.359+0000][20967][gc,age] GC(0) Desired survivor size 17432576 bytes, new threshold 6 (max threshold 6)
> [2020-03-25T13:56:25.359+0000][20967][gc,age] GC(0) Age table with threshold 6 (max threshold 6)
> [2020-03-25T13:56:25.360+0000][20967][gc,age] GC(0) - age 1: 12866528 bytes, 12866528 total
> [2020-03-25T13:56:25.360+0000][20967][gc,heap] GC(0) ParNew: 272640K->12716K(306688K)
> [2020-03-25T13:56:25.360+0000][20967][gc,heap] GC(0) CMS: 0K->0K(1756416K)
> [2020-03-25T13:56:25.360+0000][20967][gc,metaspace] GC(0) Metaspace: 20258K->20258K(1067008K)
> [2020-03-25T13:56:25.360+0000][20967][gc] GC(0) Pause Young (Allocation Failure) 266M->12M(2014M) 17.420ms
> [2020-03-25T13:56:25.360+0000][20967][gc,cpu] GC(0) User=0.04s Sys=0.00s Real=0.02s
> 
> ```

If my understanding is correct regarding GC(0) Pause Young (Allocation Failure), there is not enough memory to properly work.

How should I change the java memory settings to avoid allocation failure?

my ES coordinating node configuration

> ```
> cluster.name: $myclustername
> path.data: /var/lib/elasticsearch
> path.logs: /var/log/elasticsearch
> network.host: localhost
> http.port: 9200
> transport.host: $hostipaddress
> transport.tcp.port: 9300
> discovery.seed_hosts: ["$hostarelistedhere"]
> xpack.security.enabled: true
> xpack.security.transport.ssl.enabled: true
> xpack.security.transport.ssl.verification_mode: certificate
> xpack.security.transport.ssl.keystore.path: /etc/elasticsearch/elastic-certificates.p12
> xpack.security.transport.ssl.truststore.path: /etc/elasticsearch/elastic-certificates.p12
> node.master: false
> node.data: false
> node.ingest: false
> node.ml: false
> 
> ```

Thanks,  
Andras

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [March 25, 2020, 2:59pm UTC](https://discuss.elastic.co/t/elasticsearch-coordinating-node-gc-log/224994/2 "2020-03-25T14:59:54Z")

</div>

This is normal behaviour. I don't think there's anything to worry about if you're seeing a 0.02s GC every minute.

---

<div class="post-metadata">

**Author:** ![andras.vecsi](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@andras.vecsi](https://discuss.elastic.co/u/andras.vecsi)\
**Post date:** [March 27, 2020, 11:21am UTC](https://discuss.elastic.co/t/elasticsearch-coordinating-node-gc-log/224994/3 "2020-03-27T11:21:12Z")

</div>

I had to update my knowledge for Java13. Since java9 lot of things changed regarding GC.

Thanks.

---

<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:** [April 24, 2020, 11:21am UTC](https://discuss.elastic.co/t/elasticsearch-coordinating-node-gc-log/224994/4 "2020-04-24T11:21:20Z")

</div>

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