[
https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801705#action_12801705
]
dhruba borthakur commented on HDFS-839:
---------------------------------------
> However, if it only synchronizes block reports or not sync all heartbeats,
If we do this, then it will have some impact on the failover times, right? At
the time of failover, the backupnode will not have all the information it
needs; it will have to gather those missing pieces of information before it can
start servicing request, isn't it?
> You could dedicate a link for NN to backup node communication to improv
if all communication from datanodes to backupnodes flow via the NN, then in the
case of NN death, the backup nodes might not have all the
latest-and-greatest-data that was sent from the datanodes, isn't it?
> The NameNode should forward block reports to BackupNode
> -------------------------------------------------------
>
> Key: HDFS-839
> URL: https://issues.apache.org/jira/browse/HDFS-839
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: name-node
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
>
> The BackupNode (via HADOOP-4539) receives a stream of transactions from
> NameNode. However, the BackupNode does not have block locations of blocks. It
> would be nice if the NameNode can forward all block reports (that it receives
> from DataNodes) to the BackupNode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
