I opened issue #7836:
https://github.com/elasticsearch/elasticsearch/issues/7836.
On Monday, September 22, 2014 9:27:47 PM UTC-7, Otis Gospodnetic wrote:
Hi,
It sounds like every single ES deployment out there suffers from this, or
am I missing something? Is there an ES issue where this
Otis, from what I understand, the default size for the cache is unbounded,
so cache eviction should not occur due to inconsistent range checks in the
default case.
--
Ivan
On Mon, Sep 22, 2014 at 9:27 PM, Otis Gospodnetic
otis.gospodne...@gmail.com wrote:
Hi,
It sounds like every single ES
Indeed, only instances with a value (greater than 0) specified for
indices.fielddata.cache.size are affected. This is what triggers the use of
Guava's eviction-based-on-size feature[1]
Philippe
[1]
Hi Philippe,
Over the weekend I coded up a simple change to the Guava size-based
eviction algorithm to fix this. With my proposed change there are no API
changes and it works as a drop in replacement in ES. As you probably know
ES renames and compiles in the Guava libraries so actually
It seems I had the same
problem: https://groups.google.com/forum/#!topic/elasticsearch/2wJG5L9A8cs
On Monday, September 22, 2014 1:02:29 PM UTC-3, Craig Wittenberg wrote:
Hi Philippe,
Over the weekend I coded up a simple change to the Guava size-based
eviction algorithm to fix this. With
Yes, that sounds exactly like the same problem.
On Mon, Sep 22, 2014 at 1:24 PM, Felipe Hummel felipehum...@gmail.com
wrote:
It seems I had the same problem:
https://groups.google.com/forum/#!topic/elasticsearch/2wJG5L9A8cs
On Monday, September 22, 2014 1:02:29 PM UTC-3, Craig Wittenberg
That sounds great! I'd be happy to take a look at your change and possibly
do some testing locally. Is this hosted somewhere?
Cheers,
Philippe
On Mon, Sep 22, 2014 at 12:02 PM, Craig Wittenberg crai...@microsoft.com
wrote:
Hi Philippe,
Over the weekend I coded up a simple change to the Guava
Hi,
It sounds like every single ES deployment out there suffers from this, or
am I missing something? Is there an ES issue where this could be tracked
(even if the problem in in Guava)?
Thanks,
Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr Elasticsearch
