# Default filtercache

**URL:** <https://discuss.elastic.co/t/default-filtercache/31535>\
**Category:** Elasticsearch\
**Created:** [October 2, 2015, 10:56am UTC](https://discuss.elastic.co/t/default-filtercache/31535 "2015-10-02T10:56:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![N\_M\_10](https://avatars.discourse-cdn.com/v4/letter/n/f19dbf/32.png) [@N\_M\_10](https://discuss.elastic.co/u/N_M_10)\
**Post date:** [October 2, 2015, 10:56am UTC](https://discuss.elastic.co/t/default-filtercache/31535/1 "2015-10-02T10:56:57Z")

</div>

Each nodes elasticsearch.yml does not have any rule for filter-cache, still during load testing we found spikes in filter-cache, so is ES sets some default 10% (ES docs says default is 10%, so assume that that default setting must be in Elasticsearch.yml file but it was not there, or we must have removed it) as a filter cache size, even though it's not in our ES \*.yml file?

---

<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:** [October 3, 2015, 11:55pm UTC](https://discuss.elastic.co/t/default-filtercache/31535/2 "2015-10-03T23:55:14Z")

</div>

There are some settings like that we set even without them being in the config file.

---

<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:46pm UTC](https://discuss.elastic.co/t/default-filtercache/31535/3 "2017-07-05T23:46:52Z")

</div>