hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1973) HA: HDFS clients must handle namenode failover and switch over to the new active namenode.
Date Fri, 16 Sep 2011 23:27:08 GMT

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

Aaron T. Myers updated HDFS-1973:
---------------------------------

    Attachment: HDFS-1973-HDFS-1623.patch

Here's an updated patch which builds upon the previous patch and addresses all of the issues
I mentioned above.

The key differences between this patch and the previous:

# Take advantage of the changes in HADOOP-7635 and HDFS-2337 to enable cleanup of RPC connection
resources.
# Add the @Idempotent annotation to more methods of {{ClientProtocol}}.
# Add some appropriate synchronization to {{ConfiguredFailoverProxyProvider}}.

Please review this patch for potential inclusion in the HDFS-1623 branch.

> 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.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message