Feature Description
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.
Problem and Solution
The hdfs-native client supports HDFS High Availability (HA) via standard configuration properties such as dfs.ha.namenodes. and dfs.namenode.rpc-address...
To initialize the client, the HdfsActiveBuilder can be configured to target either a single active NameNode (e.g., hdfs://127.0.0.1:9000/) or an HA cluster by specifying the Namenode ID(e.g., hdfs://namenode1:9000,namenode2:9000/).
The HdfsActiveBuilder maps these URI patterns to the necessary HA configuration properties, enabling seamless access to HDFS in both standalone and HA modes.
Additional Context
No response
Are you willing to contribute to the development of this feature?
Feature Description
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.Problem and Solution
The hdfs-native client supports HDFS High Availability (HA) via standard configuration properties such as dfs.ha.namenodes. and dfs.namenode.rpc-address...
To initialize the client, the HdfsActiveBuilder can be configured to target either a single active NameNode (e.g.,
hdfs://127.0.0.1:9000/) or an HA cluster by specifying the Namenode ID(e.g.,hdfs://namenode1:9000,namenode2:9000/).The HdfsActiveBuilder maps these URI patterns to the necessary HA configuration properties, enabling seamless access to HDFS in both standalone and HA modes.
Additional Context
No response
Are you willing to contribute to the development of this feature?