New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent too many agg buckets from causing OOM #8081
Labels
Comments
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 |
+1 |
@clintongormley do you think this can be considered fixed by #19394 ? |
@dakrone yes! Closing |
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Sep 20, 2016
This marks the "Prevent combinatorial explosion in aggregations from causing OOM" task as done in 5.0.0. Relates to elastic#8081 and elastic#19394
This still seems to happen, re-opened as #35896 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
The text was updated successfully, but these errors were encountered: