HDDS-4538: Workaround on HDDS-2823, hard code scmUuid and clusterID #1649
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
GlenGeng-awx
force-pushed
the
HDDS-4538
branch
from
6e98043 to
c88fc9d
Compare
Contributor
Author
|
@ChenSammi @nandakumar131 Please take a look at this PR. Thanks! |
nandakumar131
changed the title
nandakumar131
approved these changes
Dec 2, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
A typical SCM group consists of 3 SCMs. If each of the them has its own scmUuid and clusterID, it will cause chaos in Datanode side.
For now, we just hard code the clusterID and scmUuid on HDDS-2823, so that we can setup a SCM raft group.
We need figure out a decent solution when merging back HDDS-2823 back to master.
What is the link to the Apache JIRA
HDDS-4538
How was this patch tested?
CI