[
https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801004#action_12801004
]
Eli Collins commented on HDFS-839:
----------------------------------
bq. I am thinking that the namenode has to spend considerable horsepower to
keep forwarding block reports and blocksReceived to BackupNode. I would like to
have a HA solution without impacting the performance of the NN. Thus, the
proposal to make datanodes send blocks reports and blocks received to NN as
well as BN.
Is the rate of block creation that high? If you have n backup nodes it seems
like the network overhead of having each DN send it's block report to each
backup node on a large cluster would be higher than a stream from the NN to the
backup node. You could dedicate a link for NN to backup node communication to
improve throughput but it's hard to do something similar for DNs all over the
network.
> 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.
