Repository navigation
HDDS-16182. Extend container balancer start command with auto-config - #11906
Draft
sreejasahithi wants to merge 1 commit into
Draft
sreejasahithi wants to merge 1 commit into
sreejasahithi wants to merge 1 commit into
Conversation
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?
This PR adds --auto-config (and optional --profile) to ozone admin containerbalancer start. The command reads current datanode usage from SCM, runs the existing container balancer advisor (MEDIUM profile by default), and starts the balancer with the recommended settings. Explicit flags (for example -i, -e, size and timeout options) still apply during recommendation and at start. If the cluster is already balanced, it prints a message and does not start the balancer.
What is the link to the Apache JIRA
HDDS-16182
How was this patch tested?
Unit tests in TestContainerBalancerSubCommand for --auto-config, overrides, --profile validation, and the balanced-cluster no-start path.
Green CI : https://github.com/sreejasahithi/ozone/actions/runs/41023328534