# Field Data Cache Evictions

**URL:** <https://discuss.elastic.co/t/field-data-cache-evictions/44980>\
**Category:** Elasticsearch\
**Created:** [March 21, 2016, 11:29am UTC](https://discuss.elastic.co/t/field-data-cache-evictions/44980 "2016-03-21T11:29:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![anshulagrawal](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@anshulagrawal](https://discuss.elastic.co/u/anshulagrawal)\
**Post date:** [March 21, 2016, 11:29am UTC](https://discuss.elastic.co/t/field-data-cache-evictions/44980/1 "2016-03-21T11:29:44Z")

</div>

Hi,

We have our field data configured at 40% of available heap size (which is currently configured to 122 GB) which comes to 48.8 GB. But we are seeing evictions at a number of 835 and field data reaches 47.7 B easily.

Our heap usage under this condition is at 95% and we see long running full GCs with G1GC configured. ALso the CPU usage went upto 80% during this time.

I wanted to know how much load can every eviction cause on the system.

Thanks,  
Asnhul

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 21, 2016, 10:05pm UTC](https://discuss.elastic.co/t/field-data-cache-evictions/44980/2 "2016-03-21T22:05:39Z")

</div>

> [@anshulagrawal](#):
>
> heap size (which is currently configured to 122 GB)

Wow.

> [@anshulagrawal](#):
>
> Our heap usage under this condition is at 95% and we see long running full GCs with G1GC configured. ALso the CPU usage went upto 80% during this time.

Then you probably need more heap, or ideally, more nodes.

---

<div class="post-metadata">

**Author:** ![anshulagrawal](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@anshulagrawal](https://discuss.elastic.co/u/anshulagrawal)\
**Post date:** [March 22, 2016, 6:02am UTC](https://discuss.elastic.co/t/field-data-cache-evictions/44980/3 "2016-03-22T06:02:16Z")

</div>

Yes, we have plans in line to move to 30GB nodes and scale horizontally. But befor ethat we wanted to understand what is consuming our heap so much, considering field data is limited to 48.8 GB per host and filter cache to 12.2 GB, that easily leaves room for 60 GB of heap available.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 22, 2016, 7:04am UTC](https://discuss.elastic.co/t/field-data-cache-evictions/44980/4 "2016-03-22T07:04:45Z")

</div>

If you want to be sure, take a heap dump and analyse it.

---

<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 5, 2017, 11:06pm UTC](https://discuss.elastic.co/t/field-data-cache-evictions/44980/5 "2017-07-05T23:06:24Z")

</div>