HDDS-8358. Fix the space usage comparator in ContainerBalancerSelectionCriteria #4527
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?
ContainerBalancerSelectionCriteriahas a ComparatororderContainersByUsedByteswhich is used for comparing containers on the basis of used space. This comparator callsisContainerMoreUsed, which does not have consistent behaviour when used space for two containers is equal.This bug was exposed when fixing the setup of
TestContainerBalancerTask.createReplicasForContainers()inTestContainerBalancerTaskcreates additional container replicas but does not add them todatanodeToContainersMap, the map being used to track these. This PR intends to fix the bug and the test setup.What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8358