# \[Yesterday Pushed\]: Caching when using FS base store

**URL:** <https://discuss.elastic.co/t/yesterday-pushed-caching-when-using-fs-base-store/2862>\
**Category:** Elasticsearch\
**Created:** [March 23, 2010, 11:57pm UTC](https://discuss.elastic.co/t/yesterday-pushed-caching-when-using-fs-base-store/2862 "2010-03-23T23:57:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [March 23, 2010, 11:57pm UTC](https://discuss.elastic.co/t/yesterday-pushed-caching-when-using-fs-base-store/2862/1 "2010-03-23T23:57:34Z")

</div>

Explained here:  
[http://github.com/elasticsearch/elasticsearch/issues/closed#issue/82](http://github.com/elasticsearch/elasticsearch/issues/closed#issue/82). I  
really like this feature, as it gives the flexability of storing part of the  
index in memory, like the term information file (tis). Think, in database  
terms, storing the index in memory while the actual data is stored on file  
system.

Note, storing in memory parts (or the whole index, as with the memory store)  
has no affect on long term persistency (translate: you will not loose data)  
thanks to the gateway (write behind) concept in elasticsearch.

-shay.banon

---

<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 6, 2017, 4:25am UTC](https://discuss.elastic.co/t/yesterday-pushed-caching-when-using-fs-base-store/2862/2 "2017-07-06T04:25:09Z")

</div>