# Identiying how Memory is being used in ES

**URL:** https://discuss.elastic.co/t/identiying-how-memory-is-being-used-in-es/85322
**Category:** Elasticsearch
**Created:** [May 11, 2017, 3:40am UTC](https://discuss.elastic.co/t/identiying-how-memory-is-being-used-in-es/85322 "2017-05-11T03:40:15Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Barto\_Rael](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@Barto\_Rael](https://discuss.elastic.co/u/Barto_Rael)
#### Post date: [May 11, 2017, 3:40am UTC](https://discuss.elastic.co/t/identiying-how-memory-is-being-used-in-es/85322/1 "2017-05-11T03:40:15Z")

</div>

Hi All,

We are using 15 node cluster with 12 GB Heap Size allocated per node. We have set bootstrap.mlockall: true to avoid memory swapping.

When I am monitoring cluster via Marvel plugin then it is showing that all nodes are using 70-75% of JVM memory so I digged into metrics to measure where this memory is being used. We don't have defined property "indices.fielddata.cache.size" in configuration so there is no limit for fielddata memory size from us. I was expecting that entire JVM memory must be used by fielddata but it is not the case.

I checked the fielddata memory usage by "GET /\_nodes/stats/indices/fielddata" which is showing that each node is using 4 GB memory which is only 33% of total memory (12 GB) and count is evictions is 0.

Could anyone help me to identify how this memory is being utilized by ES?

---

<div class="post-metadata">

### Author: ![Hanish\_Bansal](https://avatars.discourse-cdn.com/v4/letter/h/e36b37/32.png) [@Hanish\_Bansal](https://discuss.elastic.co/u/Hanish_Bansal)
#### Post date: [May 13, 2017, 2:58am UTC](https://discuss.elastic.co/t/identiying-how-memory-is-being-used-in-es/85322/2 "2017-05-13T02:58:07Z")

</div>

Any update of above query?

What is default size of field data cache? is it same as total Heap size or not ?

In system logs, we are getting below logs which indicates that most of memory is used by old GC pool.

[2017-05-13 06:45:42,317][WARN][monitor.jvm] [node2] [gc][old][6851992][21024] duration [11.2s], collections [1]/[11.7s], total [11.2s]/[27.5m], memory [11.3gb]-\>[8.3gb]/[14.9gb], all\_pools {[young] [450.6mb]-\>[49.3mb]/[532.5mb]}{[survivor] [66.5mb]-\>[0b]/[66.5mb]}{[old] [10.8gb]-\>[8.2gb]/[14.3gb]}

Can we do something to clear GC old pool memory?

---

<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: [June 10, 2017, 3:05am UTC](https://discuss.elastic.co/t/identiying-how-memory-is-being-used-in-es/85322/3 "2017-06-10T03:05:05Z")

</div>

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