Facet cache size and other memory metrics


(smonasco-2) #1

Hi,

We're having problems with some nodes hitting the maximum heap size and
were looking into ways to get visibility into the field cache impact of
different indexes/shards.

Any suggestions?

--Shannon Monasco

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6d95699e-b6cf-4553-907e-8aa029f045a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(smonasco-2) #2

For instance I think I remember some plugin that would give you an idea how
big an impact a facet might have on your field cache, and I think that was
suppose to become part of Elasticsearch itself, but I may be dreaming.

On Tuesday, June 17, 2014 4:06:35 PM UTC-6, smonasco wrote:

Hi,

We're having problems with some nodes hitting the maximum heap size and
were looking into ways to get visibility into the field cache impact of
different indexes/shards.

Any suggestions?

--Shannon Monasco

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a7998f97-36dc-45fd-86a4-28eae0a9eb90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(smonasco-2) #3

This has something like what I'd like to find in the Cache stats per field
section https://github.com/bleskes/elasticfacets , but I'm unsure if it's
any good for 1.x

On Tuesday, June 17, 2014 4:10:13 PM UTC-6, smonasco wrote:

For instance I think I remember some plugin that would give you an idea
how big an impact a facet might have on your field cache, and I think that
was suppose to become part of Elasticsearch itself, but I may be dreaming.

On Tuesday, June 17, 2014 4:06:35 PM UTC-6, smonasco wrote:

Hi,

We're having problems with some nodes hitting the maximum heap size and
were looking into ways to get visibility into the field cache impact of
different indexes/shards.

Any suggestions?

--Shannon Monasco

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d869473a-96ff-4169-a96a-1fd0e11681d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #4