Hi all, I'm trying to figure out why some of my elasticsearch cluster data nodes have frequent long GC Pauses, which in one month can actually cause around 1 or 2 daily Green -> Red State Changes due to "failed to ping" DataNode sort of incidents. JVM: OpenJDK Runtime Environment (build 1.8.0_101-…

Did you try to reduce the heap size instead of increasing it? It seems like you have quite a lot of heap and not much of it is utilized and under heavy load it might accumulate quite a bit of garbage.

Indeed some Old Gen GCs are able to release almost half of used JVM Heap (accumulation?). To what heap size would you fallback to in this case? 16GB?

When I look at the heap graph that you posted I see pretty healthy sawtooth pattern going between 10G and 17G. So, I feel like 16G would be pretty safe first iteration after which I would suggest checking how the system is behaving and possibly trying again. From the graph that you posted I see tha…

Discuss the Elastic Stack

Finding why long GCs occur and fixing efficiency issues in Elastic Cluster

Elastic Stack Elasticsearch

system (system) Closed January 25, 2019, 10:09pm 5

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

Topic		Replies	Views
ElasticSearch gc performance on cluster Elasticsearch	3	688	July 5, 2017
Long GC pauses with ES 1.3.4 Elasticsearch	12	1576	July 5, 2017
Very long GC Elasticsearch	11	6965	July 6, 2017
Long gc pause happened on es1.7.0 plus jdk8u40 Elasticsearch	15	773	July 5, 2017
Long GC pauses on data nodes Elasticsearch	9	2684	April 18, 2019

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Finding why long GCs occur and fixing efficiency issues in Elastic Cluster

Related topics