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, 02 Sep 2011 07:20:11 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.0.patch

Here's a preliminary patch (not intended for commit) to give people an idea how this will

The main things this is missing before it could reasonably be committed are:

# It currently doesn't handle clean-up of fail-over client resources at all. The way RPC resource
cleanup currently works is by looking up the appropriate RPCEngine given a protocol class,
and leaving it up to that class's InvocationHandler. This implicitly assumes that there is
a one-to-one mapping from protocol class -> invocation handler, which is no longer true.
It's not obvious to me at the moment what's the best way to deal with this.
# Currently only one of the {{ClientProtocol}} methods is annotated with the @Idempotent annotation.
# It currently doesn't handle concurrent connections at all.

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


View raw message