-
Notifications
You must be signed in to change notification settings - Fork 579
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
Partition autobalancer full disk test #5839
Merged
ztlpn
merged 8 commits into
redpanda-data:dev
from
ztlpn:partition-autobalancer-test-full-disk
Aug 5, 2022
Merged
Partition autobalancer full disk test #5839
ztlpn
merged 8 commits into
redpanda-data:dev
from
ztlpn:partition-autobalancer-test-full-disk
Aug 5, 2022
Commits on Aug 5, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 4bd1500 - Browse repository at this point
Copy the full SHA 4bd1500View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5eff865 - Browse repository at this point
Copy the full SHA 5eff865View commit details -
Configuration menu - View commit details
-
Copy full SHA for 849b684 - Browse repository at this point
Copy the full SHA 849b684View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8f9e4b8 - Browse repository at this point
Copy the full SHA 8f9e4b8View commit details -
c/partition_balancer: introduce hard_max_disk_usage_ratio
When moving partitions away from unavailable nodes it is desireable to violate disk ratio that we use to determine when we need to move nodes away from a node - this will allow us to save data if we have some free space left. But we shouldn't go to 100%, so we use the storage_space_alert_free_threshold_percent config value to determine the hard limit.
Configuration menu - View commit details
-
Copy full SHA for 5f65dd0 - Browse repository at this point
Copy the full SHA 5f65dd0View commit details -
c/partition_balancer: take already planned reallocations into account
Previously there was a following bug with moving partitions away from nodes with full disks: because the planner tries to move all replicas in a set from "bad" nodes in one reallocation, if we don't take into account previous reallocations, we might consider that some node is still full even if we have already planned several moves away from it. This lead to excessive movements being planned: when a full node became almost empty after executing a batch of reallocations. In this commit we use "final" node disk usage (after all reallocations are finished) where appropriate.
Configuration menu - View commit details
-
Copy full SHA for dd9aa7c - Browse repository at this point
Copy the full SHA dd9aa7cView commit details -
Configuration menu - View commit details
-
Copy full SHA for d58ecbc - Browse repository at this point
Copy the full SHA d58ecbcView commit details -
Configuration menu - View commit details
-
Copy full SHA for a484b37 - Browse repository at this point
Copy the full SHA a484b37View commit details
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.