Hi,
We have about 30 node elasticsearch cluster. We often run in to out of
memory issue and when I look in the JVM memory which is usually around
75-80% which is 24-25 gigs of 30 gigs heap. The filter cache and field
cache add to up 5GB on a node, I'm trying to understand whats the other
15-20
All,
It was mentioned
here
http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/children-agg.html
that the support for parent aggregation is not currently supported. Any
ideas on when it will be supported or where its in the roadmap ?
Are there any workarounds for that ?
Thank
h mohan
>>>> wrote:
>>>>
>>>>> Hi ,
>>>>>
>>>>> What is the memory for each of these machines ?
>>>>> Also see if there is any correlation between garbage collection and
>>>>> the time this anomaly happens
Hi all,
We recently had a cascading cluster failure. From 16:35 to 16:42 the
cluster went red and recovered it self. I can't seem to find any obvious
logs around this time.
The cluster has about 19 nodes. 9 physical boxes running two instances of
elasticsearch. And one vm as balancer for i
>
> I think I figured it out. Each aggs sections sub divides the data. First
> aggs buckets all the nested docs. Second aggs restricts the bucket to a
> filter. Third aggs run the terms facet on it.
>
"aggs": {
"foo": {
"nested": {
"path": "rdata"
},
"aggs": {
Hi all,
I'm using ES 1.3.2
My document structure
{
"mapids" : [mapid1, mapid2,mapid3],
"rdata" : [ {mapid1: value1},
{mapid2:value2},{mapid3:value3} ]
}
We are trying to migrate to the new aggregation framework and I'm tryin
