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.
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
@clintongormley do you think this can be considered fixed by #19394 ?
@dakrone yes! Closing
[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