kvserver: make allocator's disk utilization thresholds tunable #79736
Conversation
This file contains 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
The allocator has two different disk space utilization thresholds that it uses to determine a) when candidate stores are too full to be receiving any new replicas, and b) when _existing_ stores are too full and should start shedding replicas. Previously, these were static constants. This commit makes them tunable. Resolves cockroachdb#79461 Release note: none
|
This change is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The allocator has two different disk space utilization thresholds that it uses
to determine a) when candidate stores are too full to be receiving any new
replicas, and b) when existing stores are too full and should start shedding
replicas. Previously, these were static constants. This commit makes them
tunable.
Resolves #79461
Release note: none