Facet Bug - Memory dropped from 80GB to 5GB

Elastic Stack Elasticsearch
1

Hi,

I do not know if it's a bug or even implementation decision.

The fieldCache cache uses only the name of the field that was supposed
to be using the field name plus the name of the type, with that'd be
avoiding making unnecessary cache.
I had this problem and my memory consumption dropped from 80GB to 5GB.

Gustavo Maia

--

2

Regardless of a different type, in Lucene it will end up under the same field name. What did you change? Are you loading for fields only for a specific type? This will generically cause more memory usage as you start to facet across types. I would say that it smells like you are using the multi types option wrongly?

On Jan 24, 2013, at 1:21 PM, Gustavo Maia gustavobbmaia@gmail.com wrote:

Hi,

I do not know if it's a bug or even implementation decision.

The fieldCache cache uses only the name of the field that was supposed
to be using the field name plus the name of the type, with that'd be
avoiding making unnecessary cache.
I had this problem and my memory consumption dropped from 80GB to 5GB.

Gustavo Maia

--