[
https://issues.apache.org/jira/browse/HDFS-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916510#comment-13916510
]
Haohui Mai commented on HDFS-6034:
----------------------------------
{code}
- if (!namesystem.getRegistrationID().equals(nodeReg.getRegistrationID())) {
- LOG.warn("Invalid registrationID - expected: "
- + namesystem.getRegistrationID() + " received: "
- + nodeReg.getRegistrationID());
{code}
Without this code the standby NN will not bail out if it finds that its
clusterID is inconsistent with the one in active NN / JN.
> DN registration should use DataNodeLayoutVersion instead of
> NameNodeLayoutVersion
> ---------------------------------------------------------------------------------
>
> Key: HDFS-6034
> URL: https://issues.apache.org/jira/browse/HDFS-6034
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, ha, hdfs-client, namenode
> Affects Versions: HDFS-5535 (Rolling upgrades)
> Reporter: Haohui Mai
> Assignee: Tsz Wo (Nicholas), SZE
> Attachments: h6034_20140228.patch
>
>
> Currently the registrationID is in the form of
> {{BlockPoolID-NNLayoutVersion}}. When the NN bumps the layout version during
> rolling upgrade, the DNs will fail to register with the new NN and exit,
> regardless whether the new software version is used.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
