HDDS-13586. [DiskBalancer] Refactor DiskBalancer to remove unused methods and improve naming #8956
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?
1. Improve data structures and type safety :
Objects.requireNonNull(..)instead ofPreconditions.checkNotNull(..).RuntimeExceptioninstead throwIOException.2. Replace the use of Optional for method parameters in DiskBalancer:
As a general rule, parameters should be explicitly required or nullable, not wrapped in an Optional. For context, see: https://www.reddit.com/r/java/comments/sat1j4/opinions_on_using_optional_as_parameter/
3. Cleanup of Dead Code:
new Container.importContainerData(Path containerPath)method since it is never used.Container.copyContainerDatatocopyContainerDirectory. As, it sounds like copy/import the ContainerData class.4. parameterize disk balancer related unit tests with different container schema versions.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-13586
How was this patch tested?
Passed Existing Tests.