# Cluster outage with old-gen size increasing

**URL:** <https://discuss.elastic.co/t/cluster-outage-with-old-gen-size-increasing/215229>\
**Category:** Elasticsearch\
**Created:** [January 16, 2020, 12:28am UTC](https://discuss.elastic.co/t/cluster-outage-with-old-gen-size-increasing/215229 "2020-01-16T00:28:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![musfiqur](https://avatars.discourse-cdn.com/v4/letter/m/3bc359/32.png) [@musfiqur](https://discuss.elastic.co/u/musfiqur)\
**Post date:** [January 16, 2020, 12:28am UTC](https://discuss.elastic.co/t/cluster-outage-with-old-gen-size-increasing/215229/1 "2020-01-16T00:28:35Z")

</div>

Hi,  
We are seeing logs like this in our ElasticSearch 6.7:  
[gc][young][678215][290288] duration [718ms], collections [1]/[1s], total [718ms]/[4.5h], memory [9.6gb]-\>[10.3gb]/[30.1gb], all\_pools {[young] [108.4mb]-\>[332.8mb]/[998.5mb]}{[survivor] [124.7mb]-\>[124.7mb]/[124.7mb]}{[old] [9.3gb]-\>[9.8gb]/[29gb]}  
The timing coincides with a cluster outage. What does the above log mean/indicate? Why the garbage collection is taking long?  
-Musfiqur

---

<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:** [February 13, 2020, 12:28am UTC](https://discuss.elastic.co/t/cluster-outage-with-old-gen-size-increasing/215229/2 "2020-02-13T00:28:52Z")

</div>

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