Mahipal Jupalli created HDFS-10421: -------------------------------------- Summary: The nameservice for a Hadoop Namenode HA should be discoverable across clusters Key: HDFS-10421 URL: https://issues.apache.org/jira/browse/HDFS-10421 Project: Hadoop HDFS Issue Type: New Feature Components: ha, hdfs-client Reporter: Mahipal Jupalli Priority: Minor
Name service configured in NameNode HA mode, should be discoverable across clusters without having to restart all the clusters every time a new cluster is deployed. Solution #1: One solution would be to add the nameservice configurations to all the hdfs-site.xml files in the clusters involved. Cons: We cannot restart all clusters every time we deploy a new cluster. We are developing a custom class to extend org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider, this custom provider will make a REST call to fetch any additional nameservice configurations and cache them locally (expires on a configured time limit). This will fix the issue to resolve the name service across clusters and also eliminate the need to restart all the clusters whenever a new cluster is configured. Please provide your inputs. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org