# CPU usage slowly climbs until ES needs a restart

**URL:** <https://discuss.elastic.co/t/cpu-usage-slowly-climbs-until-es-needs-a-restart/38276>\
**Category:** Elasticsearch\
**Created:** [January 3, 2016, 3:59pm UTC](https://discuss.elastic.co/t/cpu-usage-slowly-climbs-until-es-needs-a-restart/38276 "2016-01-03T15:59:45Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![travisbell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/travisbell/32/6272_2.png) [@travisbell](https://discuss.elastic.co/u/travisbell)\
**Post date:** [April 11, 2016, 4:55pm UTC](https://discuss.elastic.co/t/cpu-usage-slowly-climbs-until-es-needs-a-restart/38276/5 "2016-04-11T16:55:24Z")

</div>

For the sake of any other potential user searching around and finding this thread, over on this other post [here](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229/50?u=travisbell) it was mentioned that switching from G1 GC to CMS solved another user having a similar issue as this. We made this change on our stack and low and behold, this problem went away.

We even ran both GC's simultaneously on different nodes and the G1 nodes continued to act up while the CMS node was fine. It's been 15 days now and the CMS node hasn't needed a restart. Hope this can help any one who comes across this bizarre problem.

---

_[View the full topic](https://discuss.elastic.co/t/cpu-usage-slowly-climbs-until-es-needs-a-restart/38276)._