Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 26 Sep 2011 23:37:13 +0000 (UTC)
From: "Aaron T. Myers (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1972670752.687.1317080233238.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1981375905.30968.1305909407420.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1973) HA: HDFS clients must handle
 namenode failover and switch over to the new active namenode.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115036#comment-13115036 ] 

Aaron T. Myers commented on HDFS-1973:
--------------------------------------

bq. A general note: this failover proxy provider doesn't get passed enough info to choose different configs based on the "logical URI". For example, if I have two clusters, foo and bar I'd expect to be able to configure dfs.ha.namenodes.foo separately from dfs.ha.namenodes.bar after setting both of dfs.client.failover.proxy.provider.foo|bar.

I've filed HDFS-2367 to address this issue.
                
> HA: HDFS clients must handle namenode failover and switch over to the new active namenode.
> ------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1973
>                 URL: https://issues.apache.org/jira/browse/HDFS-1973
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Suresh Srinivas
>            Assignee: Aaron T. Myers
>         Attachments: HDFS-1973-HDFS-1623.patch, HDFS-1973-HDFS-1623.patch, hdfs-1973.0.patch
>
>
> During failover, a client must detect the current active namenode failure and switch over to the new active namenode. The switch over might make use of IP failover or some thing more elaborate such as zookeeper to discover the new active.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira