# Constant Garbage Collecting

**URL:** <https://discuss.elastic.co/t/constant-garbage-collecting/276180>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [June 16, 2021, 5:44pm UTC](https://discuss.elastic.co/t/constant-garbage-collecting/276180 "2021-06-16T17:44:23Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Tim\_Mobley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tim_mobley/32/94741_2.png) [@Tim\_Mobley](https://discuss.elastic.co/u/Tim_Mobley)\
**Post date:** [June 16, 2021, 8:43pm UTC](https://discuss.elastic.co/t/constant-garbage-collecting/276180/5 "2021-06-16T20:43:22Z")

</div>

That's what it's seeing but it's not the case. I have 2 hot data nodes and 1 cold (on this cluster), but because of this issue they keep "leaving" the cluster. So the output you're seeing isn't correct. As to the heap, I have been following the recommendation to use half the physical memory. So on the three data nodes I upped the RAM to 48GB and set the min/max to 24GB in java.options.

-- I forgot to answer your question about the shards. I've been trying to do that, but my [other issue](https://discuss.elastic.co/t/request-body-is-required/275691) is that I can't use the reindex API. But I have been forcemerging to at least reduce the segments. That works at least.

---

_[View the full topic](https://discuss.elastic.co/t/constant-garbage-collecting/276180)._
