HDDS-15257. [DiskBalancer] Add CLOSING state to the "not movable" check#10254
Merged
Conversation
ChenSammi
approved these changes
May 13, 2026
Contributor
ChenSammi
left a comment
There was a problem hiding this comment.
Thanks @Gargi-jais11 .
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
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.
What changes were proposed in this pull request?
isOpenToWriteState(state) only returns true for
OPENandRECOVERING:CLOSING is not covered. So when this validation in DiskBalancerConfiguration runs, it only blocks OPEN, RECOVERING, and DELETED. A user who configures
movableContainerStates = CLOSINGwould not get an error — the config would silently allow DiskBalancer to try to move containers in CLOSING state.Fix:
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-15257
How was this patch tested?
Updated unit test and tested manually.