-
Notifications
You must be signed in to change notification settings - Fork 25.2k
java.lang.OutOfMemoryError: Java heap space #35482
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
Comments
Pinging @elastic/es-search-aggs |
Can you please share what the request looks like? |
|
Pinging @elastic/es-analytics-geo |
That's a term aggregation that is trying to get back 1 million buckets within a date histogram aggregation. So, it's seems like an aggs-related circuit-breaker issue to me. @dliappis was it relabeled as |
@imotov thanks for the clarification, indeed had a chat with @mayya-sharipova about the right team, but I think geo came by mistake. I'll relabel it as :Analytics/Aggregations. |
I suspect this is just a case of #28220, where our agg framework does a poor job estimating the memory cost of each agg type. It underestimates some aggs, and over-estimates others. The newish |
Uh oh!
There was an error while loading. Please reload this page.
Describe the feature:
When I use nested aggregation of dsl return large amount of data,then elasticsearch error: java.lang.OutOfMemoryError: Java heap space.
Elasticsearch version (
bin/elasticsearch --version
):6.3.0
Plugins installed: []
JVM version (
java -version
):jdk_1.8.152
OS version (

uname -a
if on a Unix-like system):linux
Description of the problem including expected versus actual behavior:
1.Without any operating,why ramCurrent is full.
2.Then query dsl frequently,elasticsearch happened error :java.lang.OutOfMemoryError: Java heap space
3.ramCurrent include what?
4.aggregation used which ram,filedata cache or query cache or request cache?
Steps to reproduce:
Please include a minimal but complete recreation of the problem, including
(e.g.) index creation, mappings, settings, query etc. The easier you make for
us to reproduce it, the more likely that somebody will take the time to look at it.
1.query node state
2.query dsl frequently
3.elasticsearch error
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: