# Where the filter cache memory allocated?

**URL:** <https://discuss.elastic.co/t/where-the-filter-cache-memory-allocated/51549>\
**Category:** Elasticsearch\
**Created:** [June 1, 2016, 10:50am UTC](https://discuss.elastic.co/t/where-the-filter-cache-memory-allocated/51549 "2016-06-01T10:50:19Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Selvam\_ayyanar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/selvam_ayyanar/32/11101_2.png) [@Selvam\_ayyanar](https://discuss.elastic.co/u/Selvam_ayyanar)\
**Post date:** [June 1, 2016, 10:50am UTC](https://discuss.elastic.co/t/where-the-filter-cache-memory-allocated/51549/1 "2016-06-01T10:50:19Z")

</div>

Hi Team,

the filter cache memory is allocated from heap?

if it is allocated from heap, is the possibility to affect the gc?

---

<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:** [June 2, 2016, 1:08am UTC](https://discuss.elastic.co/t/where-the-filter-cache-memory-allocated/51549/2 "2016-06-02T01:08:37Z")

</div>

It is taken from heap but it isn't GCd. So when something goes into filter cache, it takes away heap for other things.

It shouldn't be a major issue though, the bitsets are very efficient.

---

<div class="post-metadata">

**Author:** ![Selvam\_ayyanar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/selvam_ayyanar/32/11101_2.png) [@Selvam\_ayyanar](https://discuss.elastic.co/u/Selvam_ayyanar)\
**Post date:** [June 3, 2016, 7:36am UTC](https://discuss.elastic.co/t/where-the-filter-cache-memory-allocated/51549/3 "2016-06-03T07:36:39Z")

</div>

Hi @warkolm,  
Thanks for you reply, we are facing gc issue on prod servers.

1. we are using elasticsearch 1.3.7
2. we allocated 10G for each clusters
3. filter and field cache 30%, 20%
4. gc params like below  
-XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:CMSInitiatingOccupancyFraction=65 -XX:+UseCMSInitiatingOccupancyOnly -XX:+PrintGCDetails -verbose:gc -XX:+PrintGCDateStamps -XX:NewSize=1536m -XX:MaxNewSize=1536m -XX:SurvivorRatio=46 -XX:MaxTenuringThreshold=3

we are getting promotion failed , and concurrent mode failure gc issues. ( nearly 7 to 8 G heap usage )  
once we cleared the cache the alert gone.

can you give me suggestions...

---

<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:** [June 4, 2016, 1:50am UTC](https://discuss.elastic.co/t/where-the-filter-cache-memory-allocated/51549/4 "2016-06-04T01:50:22Z")

</div>

Upgrading would be my first recommendation, 1.3 hasn't been supported for a loooooong time.

---

<div class="post-metadata">

**Author:** ![Selvam\_ayyanar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/selvam_ayyanar/32/11101_2.png) [@Selvam\_ayyanar](https://discuss.elastic.co/u/Selvam_ayyanar)\
**Post date:** [June 4, 2016, 7:01am UTC](https://discuss.elastic.co/t/where-the-filter-cache-memory-allocated/51549/5 "2016-06-04T07:01:58Z")

</div>

But i need to know, why "the promotion failed , and concurrent mode failure" alerts gone once i cleared cache.

---

<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, 10:46pm UTC](https://discuss.elastic.co/t/where-the-filter-cache-memory-allocated/51549/6 "2017-07-05T22:46:13Z")

</div>