# Who ate my memory

**URL:** <https://discuss.elastic.co/t/who-ate-my-memory/355208>\
**Category:** Elasticsearch\
**Created:** [March 12, 2024, 7:14am UTC](https://discuss.elastic.co/t/who-ate-my-memory/355208 "2024-03-12T07:14:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lu\_pan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lu_pan/32/127225_2.png) [@lu\_pan](https://discuss.elastic.co/u/lu_pan)\
**Post date:** [March 12, 2024, 7:14am UTC](https://discuss.elastic.co/t/who-ate-my-memory/355208/1 "2024-03-12T07:14:24Z")

</div>

In my production environment, the ES cluster frequently encounters data too large exception.  
When I dumped the heap memory and analyzed it through MAT, I found the following confusing points:

- There are a large number of unreachable objects  
 ![es unreachable](https://us1.discourse-cdn.com/elastic/original/3X/5/b/5b2fbf351cb55c29bfd2ef807ffddc91cd17dc3f.png)

**May I ask when this part of memory can be recycled and what is stored there?**

---

<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:** [April 9, 2024, 7:15am UTC](https://discuss.elastic.co/t/who-ate-my-memory/355208/2 "2024-04-09T07:15:24Z")

</div>

Closed on April 9, 2024, 7:15am UTC

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