-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Add min/max size methods for MemorySizeSetting #19230
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
Open
peteralfonsi
wants to merge
4
commits into
opensearch-project:main
Choose a base branch
from
peteralfonsi:memory-max-size-setting
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
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
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.
I am wondering if there are really any real use cases of specifying the
minPercentageformemorySizeSetting. Why would be make something use minimum memory, the objective is mostly limiting the maximum amount of consumed memory by a component. Probably, that is the reason we never required explicit min/max and the default value kind of served as the maximum limitThere 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.
I'd be ok with just having it be maximum. However while checking I did find one setting
BlobStoreRepository.SNAPSHOT_REPOSITORY_DATA_CACHE_THRESHOLD(link) where they shove the parser logic into a lambda in the setting definition themselves, so that they can define a nonzero minimum of 500b, and a maximum of 0.01% of heap, so I guess there is at least some use case for a minimum memory setting.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.
That still seems like arbitrary low value to me, not minimum threshold that user really needs to set. Maybe we can assume nonzero minimum of 500b as the hardcoded minimum for memorySizeSetting. Are you planning to use any different value for fielddatacache use case?
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.
Seems strange to add an arbitrary 500 mb floor for a convenience method, right? Shouldn't we just make it as general as possible and users can choose what floor they need? Either that or only having maximum with a minimum of 0 makes sense to me.