# Aggregation job kills Elasticsearch nodes

**URL:** <https://discuss.elastic.co/t/aggregation-job-kills-elasticsearch-nodes/126980>\
**Category:** Elasticsearch\
**Created:** [April 5, 2018, 6:06pm UTC](https://discuss.elastic.co/t/aggregation-job-kills-elasticsearch-nodes/126980 "2018-04-05T18:06:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sknayar](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@sknayar](https://discuss.elastic.co/u/sknayar)\
**Post date:** [April 5, 2018, 6:06pm UTC](https://discuss.elastic.co/t/aggregation-job-kills-elasticsearch-nodes/126980/1 "2018-04-05T18:06:12Z")

</div>

We run an ES version 5.4.1 cluster. It takes in between 1-2TB of network session data (netflow processed by BRO devices) and a few other logs. We have hot nodes and warm nodes in the cluster and all works fine except we run an aggregations against a high volume log (bro-conn logs). This log contains all network session data and it is the highest volume log we have. When an aggregation job is run against this data even for a short time period (4-5) mins ES nodes crashes with java heap OutOfMemory error. I put in pretty low values for circuit breaker settings (see below), but didn't help

"indices" : {  
"breaker" : {  
"fielddata" : {  
"limit" : "20%"  
},  
"request" : {  
"limit" : "20%"  
},  
"total" : {  
"limit" : "30%"  
}  
},  
Any ideas?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 3, 2018, 6:06pm UTC](https://discuss.elastic.co/t/aggregation-job-kills-elasticsearch-nodes/126980/2 "2018-05-03T18:06:25Z")

</div>

Closed on May 3, 2018, 6:06pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.