Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Query Failure due to ResultLevelCache Population OOM #17651

Open
jtuglu-netflix opened this issue Jan 22, 2025 · 0 comments · May be fixed by #17652
Open

Query Failure due to ResultLevelCache Population OOM #17651

jtuglu-netflix opened this issue Jan 22, 2025 · 0 comments · May be fixed by #17652
Labels
Uncategorized problem report

Comments

@jtuglu-netflix
Copy link
Contributor

Please provide a detailed title (e.g. "Broker crashes when using TopN query with Bound filter" instead of just "Broker crashes").

Affected Version

31.0.1

Description

Currently, if a query's result set size is large enough, the result set serializer can OOM here when allocating large buffers. Not only will this affect one-off queries, but this causes a crash-loop on Broker nodes if they are attempting to make/cache large SegmentMetadata queries on boot.
@jtuglu-netflix jtuglu-netflix linked a pull request Jan 22, 2025 that will close this issue
Open
10 tasks
@jtuglu-netflix jtuglu-netflix changed the title ResultLevelCache Population OOM Query Failure due to ResultLevelCache Population OOM Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Uncategorized problem report
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Avoid OOM-killing query if result-level caching fails jtuglu-netflix/druid
1 participant
@jtuglu-netflix