HDDS-10440. Set new cluster ID and config instance in MiniOzoneCluster#build()
#6325
Conversation
This file contains 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
|
Thanks @adoroszlai for the contribution! |
|
Thanks @nandakumar131 for reviewing and merging this. |
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?
MiniOzoneCluster.Builderallows creating multiple cluster instances from the same builder. To avoid conflict, users (currently onlyMiniOzoneClusterProvider) need to set new cluster ID and a copy of the configuration. The goal of this change is to automatically set the cluster ID and config wheneverbuild()is called.https://issues.apache.org/jira/browse/HDDS-10440
How was this patch tested?
CI:
https://github.com/adoroszlai/ozone/actions/runs/8139597150