-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Fix resource leak for GroupBy query merge buffer when query matched result cache #17823
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
1c1dd7f
Fix resource leak for GroupBy query merge buffer when match result cache
maytasm 1327576
Fix resource leak for GroupBy query merge buffer when match result cache
maytasm b38ac1c
Add test
maytasm 43f666b
Add test
maytasm 7a2523b
Add comment
maytasm f480d51
Add test
maytasm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its quite unfortunate that the seq needs to be created to get
newResultSetIdas that is passed thru the responseContext.actually the returned seq is an empty seq in cases when the cache supposed to be used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I know.
The newResultSetId (ETag) is computed in CachingClusteredClient, which is many many layers down from ResultLevelCachingQueryRunner. It's not simple to compute that at this layer due to needing timeline, segmentServers, etc.
Also, the resultFromClient (Sequence) doesn't have a simple close() method so I end up having to call the accumulate. The Sequence is Mapped, Wrapped, etc. making it hard to access the resources/closers
But the Sequence retruend from CachingClusteredClient when the ETag matches (ResultLevelCache hits) is just an empty Sequence so this call should not be expensive.