As specified in documentation node-filter-cache <http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-cache.html#node-filter> :
The cache implements an LRU eviction policy: when a cache becomes full, the > least recently used data is evicted to make way for new data. But in source code I found filter cache implementation: - IndicesFilterCache <https://github.com/elasticsearch/elasticsearch/blob/master/src/main/java/org/elasticsearch/indices/cache/filter/IndicesFilterCache.java#L132> - FilterCacheValueWeigher <https://github.com/elasticsearch/elasticsearch/blob/master/src/main/java/org/elasticsearch/index/cache/filter/weighted/WeightedFilterCache.java#L220> So the cache will evict entries that consumes more memory. I think this policy is not the best choice cause fat entries can be used quite frequently. May be there should be several implementation of filter cache as Solr does. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/aea81973-2aa1-4f14-9832-6a1ffef3cd30%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
