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

**URL:** <https://discuss.elastic.co/t/warning-message-o-e-m-j-jvmgcmonitorservice/94976>\
**Category:** Elasticsearch\
**Created:** [July 28, 2017, 2:49pm UTC](https://discuss.elastic.co/t/warning-message-o-e-m-j-jvmgcmonitorservice/94976 "2017-07-28T14:49:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gugansankar](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gugansankar](https://discuss.elastic.co/u/gugansankar)\
**Post date:** [July 28, 2017, 2:49pm UTC](https://discuss.elastic.co/t/warning-message-o-e-m-j-jvmgcmonitorservice/94976/1 "2017-07-28T14:49:01Z")

</div>

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](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](http://10.21.92.21:5601/bundles/kibana.bundle.js?v=15117:13:4852)

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 28, 2017, 4:04pm UTC](https://discuss.elastic.co/t/warning-message-o-e-m-j-jvmgcmonitorservice/94976/2 "2017-07-28T16:04:37Z")

</div>

This indicates too much pressure on the JVM most likely.

---

<div class="post-metadata">

**Author:** ![gugansankar](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gugansankar](https://discuss.elastic.co/u/gugansankar)\
**Post date:** [July 29, 2017, 5:33am UTC](https://discuss.elastic.co/t/warning-message-o-e-m-j-jvmgcmonitorservice/94976/3 "2017-07-29T05:33:12Z")

</div>

Any workaround solution for this?

I'm using 5.4.2 version.

All of sudden, im started to see this problem

Thanks,  
Gugan.K

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 29, 2017, 5:48am UTC](https://discuss.elastic.co/t/warning-message-o-e-m-j-jvmgcmonitorservice/94976/4 "2017-07-29T05:48:21Z")

</div>

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....

---

<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:** [August 26, 2017, 5:48am UTC](https://discuss.elastic.co/t/warning-message-o-e-m-j-jvmgcmonitorservice/94976/5 "2017-08-26T05:48:29Z")

</div>

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