hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahipal Jupalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10421) The nameservice for a Hadoop Namenode HA should be discoverable across clusters
Date Wed, 18 May 2016 00:18:13 GMT

     [ https://issues.apache.org/jira/browse/HDFS-10421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mahipal Jupalli updated HDFS-10421:
-----------------------------------
    Description: 
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. Wondering if this would be a good feature to add and if so please
assign this to me. I will contribute to this issue.

  was:
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.


> 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. Wondering if this would be a good feature to add and if so
please assign this to me. I will contribute to this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message