I have the same issue. The configuration is : Two nodes, we sent them some
data (1m) and now they are running at 200%/400% around
org.elasticsearch.indices.cache.filter.IndicesFilterCache$ReaderCleaner$1.run(IndicesFilterCache.java:183)
for hours. (ES version 1.0.1)
Le vendredi 18
I'm still doing performance work and I keep seeing the CacheCleaner pop up
[1]. I don't know how much of an effect its actually having, but I imagine
its something.
It looks like entries in the cache get queued for deletion both by cache
clear commands and by readers closing. Would it make
