hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2691) HA: Tests and fixes for pipeline targets and replica recovery
Date Sat, 21 Jan 2012 09:56:39 GMT

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

Todd Lipcon commented on HDFS-2691:
-----------------------------------

Hi Dhruba. In your implementation, does the client send a special kind of packet in the data
transfer protocol which causes the DN to report the RBW replicas? Or does the client directly
contact all of the DNs to call updatePipeline, causing the RBW replicas to be filled in?
                
> HA: Tests and fixes for pipeline targets and replica recovery
> -------------------------------------------------------------
>
>                 Key: HDFS-2691
>                 URL: https://issues.apache.org/jira/browse/HDFS-2691
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>         Attachments: hdfs-2691.txt, hdfs-2691.txt
>
>
> Currently there are some TODOs around pipeline/recovery code in the HA branch. For example,
commitBlockSynchronization only gets sent to the active NN which may have failed over by that
point. So, we need to write some tests here and figure out what the correct behavior is.
> Another related area is the treatment of targets in the pipeline. When a pipeline is
created, the active NN adds the "expected locations" to the BlockInfoUnderConstruction, but
the DN identifiers aren't logged with the OP_ADD. So after a failover, the BlockInfoUnderConstruction
will have no targets and I imagine replica recovery would probably trigger some issues.

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

        

Mime
View raw message