Add HA functionality to WebHdfsClient #2230
Merged
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
Since version 2.1.0, the hdfs package allows to specify multiple namenodes (HA functionality), by passing an url containing multiple namenodes separated by ';'. This functionality is forwarded through to WebHdfsClient in this commit.
dlstadther
approved these changes
Sep 18, 2017
|
@Tarrasch As the main author of the webhdfs client, could you take a quick look at this patch? |
|
Thanks @adaitche :) |
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.
Motivation and Description
HDFS supports High Availability (HA) through the use of multiple namenodes. This is currently not supported by WebHdfsClient as it allows to specify only one namenode. Since version 2.1.0, the hdfs package allows to specify multiple namenodes, by passing an url containing multiple namenodes separated by ';'. This functionality is forwarded through to WebHdfsClient in this commit.
Have you tested this? If so, how?
I tested the HA functionality manually on a cluster with two namenodes. I did not add unit tests, as for this one would need to extend WebHdfsMiniCluster to support multiple namenodes, which is non-trivial and probably overkill.