thank you for reply ,my heap size is of 8gb for 74 gb index and yes i am
hitting circut breaker
so when i am querying or filtering before aggregations,aggregations are
passed only filtered/query output results ???
On Thursday, September 4, 2014 3:15:43 PM UTC+5:30, Colin Goodheart-Smithe
wrote:
>
> Hi,
>
> Sounds like your problem might be your heap size is too low. How much
> memory have you assigned to your heap (i.e. what have you set as
> ES_HEAP_SIZE)? To perform aggregations, Elasticsearch has to load the
> values for a field for every document into memory in a data structure
> called field cache. It sounds like you are hitting the circuit breaker
> which prevents this data structure using too much of the heap and causing
> an OOM error.
>
> Colin
>
> On Wednesday, 3 September 2014 17:58:02 UTC+1, navdeep agarwal wrote:
>>
>> hi ,
>>
>> i am bit new Elastic search ,while testing on elasticsearch's aggregation
>> feature ,i am always hitting data too large,i understand that aggregations
>> are very memory intensive , so is there any way query in ES where one
>> query's output can be ingested to aggregation so that number of input to
>> aggregation is limited . i have used filter and querying before
>> aggregations .
>>
>> i have around 60 GB index on 5 shards .
>>
>> queries i tried:
>>
>> GET **********/_search
>> {
>> "query": {"term": {
>> "file_sha2": {
>> "value": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
>> }
>> }},
>>
>> "aggs": {
>> "top_filename": {
>> "max": {
>> "field": "portalid"
>> }
>> }
>>
>> }
>> }
>>
>> -------------------------------------------------------
>>
>> GET ************/_search
>> {
>>
>> "aggs": {
>> "top filename": {
>> "filter": {"term": {
>> "file_sha2": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
>> }},
>> "aggs": {
>> "top_filename": {
>> "max": {
>> "field": "portalid"
>> }
>> }
>> }
>> }
>> }
>>
>>
>>
>> }
>>
>>
>> thanks in advance .
>>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/e3acf461-0b7c-4509-a2fb-0427ab6fc8f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
