Remove usage of RAM accounting of segments#75674
Merged
jpountz merged 21 commits intoelastic:masterfrom Jul 29, 2021
Merged
Conversation
Collaborator
|
Pinging @elastic/es-core-features (Team:Core/Features) |
3 tasks
romseygeek
approved these changes
Jul 28, 2021
Contributor
romseygeek
left a comment
There was a problem hiding this comment.
LGTM, thanks @jpountz
Contributor
Author
|
I'm making it a non-issue since it doesn't deserve a note in the changelog, unlike #75274. |
ywangd
pushed a commit
to ywangd/elasticsearch
that referenced
this pull request
Jul 30, 2021
This is a pre-requisite for the upgrade to Lucene 9, which removes the ability to estimate RAM usage of segments.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
This is a pre-requisite for the upgrade to Lucene 9, which removes the ability to estimate RAM usage of segments.
This is the same as #75274 but without the breaking change of the response format, so that we can move forward with #74057.