[ https://issues.apache.org/jira/browse/HDFS-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190339#comment-13190339 ]
dhruba borthakur commented on HDFS-2691: ---------------------------------------- In our implementation, we have implemented Option 2. can u explain what the problem is with Option 2? > 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