Modify to use multiple standby_namenodes #87
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
1 participant
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.
Signed-off-by: lion2me [email protected]
Hello, I'm Lion2me.
I am using one active namenode and two standby namenodes using the zookeeper.
While using the webhdfs plug-in, I saw that the number of standby names was fixed to one, and I am sending the corrections I made to apply to the current environment as PR.
The major changes are as follows:
Standby nameenode was made to receive multiple values based on the space.
In order to switch the nameenode, clients_standby were arranged and modified to access the index.
When failover occurred, clients_standby was iterated to find and switch available namesenodes.