feat(services/hdfs-native): service hdfs-native support high availability (HA) cluster#7248
Merged
Xuanwo merged 1 commit intoapache:mainfrom Mar 31, 2026
Merged
Conversation
cfc20c6 to
bb79ff5
Compare
0bbd83b to
c0b047a
Compare
Xuanwo
reviewed
Mar 27, 2026
Member
Xuanwo
left a comment
There was a problem hiding this comment.
Thank you for working on this! Only a small question.
c0b047a to
b39cb4d
Compare
…lity (HA) cluster Signed-off-by: qingfeng <qing.feng@zte.com.cn>
b39cb4d to
9b743fe
Compare
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
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.
Which issue does this PR close?
Closes #7246 .
Rationale for this change
The current service hdfs-native only supports connecting to HDFS clusters with a single active NameNode, such as
hdfs://127.0.0.1:9000. If the HDFS cluster is started in High Availability (HA) mode, hdfs-native will fail to connect when the active NameNode failover.What changes are included in this PR?
HdfsActiveBuilder supports both single active NameNode and High Availability (HA) modes via the name_node parameter.The builder automatically parses these URIs into standard configuration properties required to initialize the hdfs-native client.
hdfs://127.0.0.1:9000.hdfs://namenode1:9000,namenode2:9000.Additionally, any other HDFS configurations(Currently the supported configs refer to https://github.com/Kimahriman/hdfs-native) can be passed via the
optionsparameter.Are there any user-facing changes?
AI Usage Statement