[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801976#action_12801976 ]
Todd Lipcon commented on HDFS-839: ---------------------------------- I see your point about additional memory pressure for queueing up the messages to be sent. I think to resolve this issue we should lay out what consistency and reliability we need. Specifically, are lost block reports OK? If so, then the all-through-the-NN solution can simply start dropping if the queue hits some memory threshold, right? > 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.