Prevent too many agg buckets from causing OOM #8081

clintongormley opened this Issue Oct 14, 2014 · 5 comments


None yet

5 participants


Once of the last places we see OOM conditions is in aggregations, when combinatorial explosion results in too many buckets being assigned.

We need a way to catch these conditions and abort the request rather than running into OOM.

@bleskes bleskes removed the adoptme label Jun 3, 2015

We're not capturing OOM exceptions with a filters aggregations, would this count as a combinatorial aggregation that this issue would fix?


Related to #9825

blavoie commented Mar 4, 2016


dakrone commented Sep 19, 2016 edited

@clintongormley do you think this can be considered fixed by #19394 ?


@dakrone yes! Closing

@dakrone dakrone added a commit to dakrone/elasticsearch that referenced this issue Sep 20, 2016
@dakrone dakrone [DOCS] Mark combinatorial explosion in aggs as 'done'
This marks the "Prevent combinatorial explosion in aggregations from
causing OOM" task as done in 5.0.0.

Relates to #8081 and #19394
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment