Warning Message : [o.e.m.j.JvmGcMonitorService]

Elastic Stack Elasticsearch
1

All of sudden, I started to see this message on Elasticsearch log file and also unable to view the logs on Kibana frequent timedout error.

[2017-07-28T10:31:07,902][WARN ][o.e.m.j.JvmGcMonitorService] [itels1] [gc][2449] overhead, spent [2.4s] collecting in the last [2.6s]
[2017-07-28T10:31:09,771][WARN ][o.e.m.j.JvmGcMonitorService] [itels1] [gc][2450] overhead, spent [1.7s] collecting in the last [1.8s]
[2017-07-28T10:31:12,563][WARN ][o.e.m.j.JvmGcMonitorService] [itels1] [gc][2451] overhead, spent [2.6s] collecting in the last [2.7s]
[2017-07-28T10:31:14,380][WARN ][o.e.m.j.JvmGcMonitorService] [itels1] [gc][2452] overhead, spent [1.7s] collecting in the last [1.8s]
[2017-07-28T10:31:17,129][WARN ][o.e.m.j.JvmGcMonitorService] [itels1] [gc][2453] overhead, spent [2.6s] collecting in the last [2.7s]

Kibana Timedout error:
Error: Request Timeout after 30000ms
at http://10.21.92.21:5601/bundles/kibana.bundle.js?v=15117:13:4431
at http://10.21.92.21:5601/bundles/kibana.bundle.js?v=15117:13:4852

2

This indicates too much pressure on the JVM most likely.

3

Any workaround solution for this?

I'm using 5.4.2 version.

All of sudden, im started to see this problem

Thanks,
Gugan.K

4

Probably. It depends on what is causing that.
Which I can't tell as I don't know your hardware, your number of indices, shards, size, queries, mappings....

5

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