GCoverhead

Vinay_G · May 15, 2019, 4:28am

Hi,

I could see below warning message in my ES Logs.

[2017-04-07T13:34:15,260][WARN ][o.e.m.j.JvmGcMonitorService] [FBp7aLX] [gc][5157] overhead, spent [1s] collecting in the last [1.1s]

Also in our settings for ES, the refresh interval for document is set as 1s.
So because of the above warning does it mean it takes 1.1s+1s = 2.1 s to index a document?
Can someone explain more about this GC overhead and how to overcome this?

Christian_Dahlqvist · May 15, 2019, 5:44am

Which version are you using? How much heap does you nodes have assigned? What is the output of the cluster health API?

Vinay_G · May 15, 2019, 5:14pm

We are using ES 5.5.0 and we have 5 nodes.
Cluster status is yellow.

Christian_Dahlqvist · May 15, 2019, 5:56pm

What about my other questions?

Vinay_G · May 15, 2019, 11:50pm

Hi the heap is currently 40GB on each machine.

Christian_Dahlqvist · May 16, 2019, 4:58am

And what about the output of the cluster health spy?

system · June 13, 2019, 4:58am

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

Topic		Replies	Views
Constant GC warnings with small indexes Elasticsearch	4	300	December 10, 2021
Elasticsearch gc overhead Elasticsearch	1	1265	March 23, 2020
WARN Monitor.jvm Elasticsearch	4	4343	July 5, 2017
Production cluster slows down after 15-20 days of starting the services Elasticsearch	8	955	July 5, 2017
Lots of Garbage collection logs in elasticsearch 5.6 Elasticsearch	12	1471	May 13, 2020

GCoverhead

Related topics