hadoop-hdfs-issues mailing list archives

[jira] [Commented] (HDFS-1973) HA: HDFS clients must handle namenode failover and switch over to the new active namenode.

Date

Mon, 03 Oct 2011 21:02:35 GMT

[ https://issues.apache.org/jira/browse/HDFS-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119607#comment-13119607
]
Aaron T. Myers commented on HDFS-1973:
--------------------------------------
Thanks a lot for the review, Todd. Doing what you describe will require Common changes. I've
filed HADOOP-7717 to address these. Once that's committed, I'll update the patch here to remove
the synchronization from {{ConfiguredFailoverProxyProvider}}.
> 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-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