# Breakdown of Elasticsearch Heap space into its components

**URL:** <https://discuss.elastic.co/t/breakdown-of-elasticsearch-heap-space-into-its-components/132640>\
**Category:** Elasticsearch\
**Created:** [May 21, 2018, 9:54am UTC](https://discuss.elastic.co/t/breakdown-of-elasticsearch-heap-space-into-its-components/132640 "2018-05-21T09:54:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjunaidmuzammil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mjunaidmuzammil/32/56910_2.png) [@mjunaidmuzammil](https://discuss.elastic.co/u/mjunaidmuzammil)\
**Post date:** [May 21, 2018, 9:54am UTC](https://discuss.elastic.co/t/breakdown-of-elasticsearch-heap-space-into-its-components/132640/1 "2018-05-21T09:54:41Z")

</div>

Recently, I have been experimenting a lot over elastic search. During my research, I came to know ES heap usage as a key monitoring metric for ES operations. Some of the key divisions of heap include division into

1. field data cache (can be monitored from \_nodes/stats)
2. filter cache (can be monitored from \_nodes/stats)

Apart from these 2, which other buffer or caches usually takes up heap memory? I would like to know all of them, so that I can track down which cache/buffer was the culprit behind high heap usage.

---

<div class="post-metadata">

**Author:** ![mjunaidmuzammil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mjunaidmuzammil/32/56910_2.png) [@mjunaidmuzammil](https://discuss.elastic.co/u/mjunaidmuzammil)\
**Post date:** [May 22, 2018, 6:37am UTC](https://discuss.elastic.co/t/breakdown-of-elasticsearch-heap-space-into-its-components/132640/2 "2018-05-22T06:37:41Z")

</div>

@Christian_Dahlqvist @warkolm or any one here in the community who can provide some info on this?

---

<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 22, 2018, 8:41am UTC](https://discuss.elastic.co/t/breakdown-of-elasticsearch-heap-space-into-its-components/132640/3 "2018-05-22T08:41:12Z")

</div>

This forum is manned by volunteers, so **please be patient**. It is OK to bump a thread if you do not get an answer within the 2-3 days. Also please **do not ping people not already involved in the thread**.

---

<div class="post-metadata">

**Author:** ![mjunaidmuzammil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mjunaidmuzammil/32/56910_2.png) [@mjunaidmuzammil](https://discuss.elastic.co/u/mjunaidmuzammil)\
**Post date:** [May 28, 2018, 7:53am UTC](https://discuss.elastic.co/t/breakdown-of-elasticsearch-heap-space-into-its-components/132640/4 "2018-05-28T07:53:32Z")

</div>

Sure will take care of it.

Any one in the community who can guide on a way to monitor heap at a granular level?

---

<div class="post-metadata">

**Author:** ![mjunaidmuzammil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mjunaidmuzammil/32/56910_2.png) [@mjunaidmuzammil](https://discuss.elastic.co/u/mjunaidmuzammil)\
**Post date:** [June 20, 2018, 7:17am UTC](https://discuss.elastic.co/t/breakdown-of-elasticsearch-heap-space-into-its-components/132640/5 "2018-06-20T07:17:53Z")

</div>

Bumping topic so that threat doesn't close out.

---

<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:** [July 18, 2018, 7:18am UTC](https://discuss.elastic.co/t/breakdown-of-elasticsearch-heap-space-into-its-components/132640/6 "2018-07-18T07:18:05Z")

</div>

Closed on July 18, 2018, 7:18am UTC

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