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

Todd Lipcon commented on HDFS-1971:
-----------------------------------

I'll file a separate JIRA for #1 above.

Let me look into why I made that change with regard to #2

Regarding #3, the reasoning was that we used to grab references to a specific 
DatanodeProtocol proxy in BlockReceiver#verifyChunks. Now, we need to report 
that bad block to both NNs. So, it made more sense to add this new method to 
DataNode to pass the bad block info through to the correct BPOS, matching what 
we do for blockReceived, etc.
                
> HA: Send block report from datanode to both active and standby namenodes
> ------------------------------------------------------------------------
>
>                 Key: HDFS-1971
>                 URL: https://issues.apache.org/jira/browse/HDFS-1971
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: data-node, name-node
>            Reporter: Suresh Srinivas
>            Assignee: Sanjay Radia
>         Attachments: DualBlockReports.pdf, daulBr1.patch, dualBr2.patch, 
> dualBr3.patch, dualbr4.txt, dualbr5.txt
>
>
> To enable hot standby namenode, the standby node must have current 
> information for - namenode state (image + edits) and block location 
> information. This jira addresses keeping the block location information 
> current in the standby node. To do this, the proposed solution is to send 
> block reports from the datanodes to both the active and the standby namenode.

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

        

Reply via email to