[
https://issues.apache.org/jira/browse/HDFS-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159869#comment-13159869
]
Todd Lipcon commented on HDFS-1971:
-----------------------------------
bq. why removed the bpos.isALive() check that I had added: if (bpos != null &&
bpos.isAlive()) {
Since this function appears to just be used for monitoring, I think it actually
can be improved to return a deeper map, like:
{code}
[ {blockPoolId: "Unknown",
namenodes: [
{ address: "1.2.3.4:8020",
mode: CONNECTING },
{ address: "1.2.3.5:8020",
mode: CONNECTING },
]},
{blockPoolId: "BP-12345",
namenodes: [
{ address: "1.2.3.6:8020",
mode: ACTIVE },
{ address: "1.2.3.7:8020",
mode: STANDBY },
]}
]
{code}
... ie we'd include NN information even while they're still trying to handshake
(and don't know their BP ID). If that makes sense I'll file another JIRA to do
this.
bq. DatanodeRegistration getDNRegistrationByMachineName
I filed HDFS-2609 for this
> 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
