# Upgrading to 5.6.2 make GC time go through the roof

**URL:** <https://discuss.elastic.co/t/upgrading-to-5-6-2-make-gc-time-go-through-the-roof/107367>\
**Category:** Elasticsearch\
**Created:** [November 13, 2017, 10:41am UTC](https://discuss.elastic.co/t/upgrading-to-5-6-2-make-gc-time-go-through-the-roof/107367 "2017-11-13T10:41:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![moffe42](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/moffe42/32/24125_2.png) [@moffe42](https://discuss.elastic.co/u/moffe42)\
**Post date:** [November 13, 2017, 10:41am UTC](https://discuss.elastic.co/t/upgrading-to-5-6-2-make-gc-time-go-through-the-roof/107367/1 "2017-11-13T10:41:23Z")

</div>

We recently upgraded our cluster from 5.4.1 to 5.6.2 and the GC time has started to skyrocket. The GC time has over the course of 4 weeks risen 200%. Restarting the individual nodes lowers the GC time to pre-update times, but immediately starts increasing again. There is no more searches and indexing going on than before the update. I am pretty new to ES, so pointer on where to look for the cause is much appreciated.

The cluster is 6 nodes running on AWS (c4.2xl) 7 GB heap for ES, 18 shards, a replication factor of 2, size of the index is 238.1 gb and total size is 714.4gb.

Any hin ton finding out why we started seeing increased GC times is much appreciated. ![26](https://us1.discourse-cdn.com/elastic/original/3X/0/7/079667f561e11ef9051f4fa359719daa19329857.png)

---

<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:** [December 11, 2017, 10:41am UTC](https://discuss.elastic.co/t/upgrading-to-5-6-2-make-gc-time-go-through-the-roof/107367/2 "2017-12-11T10:41:23Z")

</div>

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