# Frequency old gc of some nodes in cluster

**URL:** <https://discuss.elastic.co/t/frequency-old-gc-of-some-nodes-in-cluster/180286>\
**Category:** Elasticsearch\
**Created:** [May 9, 2019, 6:07am UTC](https://discuss.elastic.co/t/frequency-old-gc-of-some-nodes-in-cluster/180286 "2019-05-09T06:07:32Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 9, 2019, 7:37am UTC](https://discuss.elastic.co/t/frequency-old-gc-of-some-nodes-in-cluster/180286/6 "2019-05-09T07:37:11Z")

</div>

Is this issue related to the same cluster discussed in [this thread](https://discuss.elastic.co/t/lots-of-disconnected-logs-and-then-oom/177758)? If so, how much data do you have in the cluster? Have you followed the guidelines laid out in [this webinar](https://www.elastic.co/webinars/optimizing-storage-efficiency-in-elasticsearch)? It also seems like you have a quite high index and shard count, which could be contributing to heap pressure. Please see [this blog post](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster) for some practical guidelines.

---

_[View the full topic](https://discuss.elastic.co/t/frequency-old-gc-of-some-nodes-in-cluster/180286)._