hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6034) DN registration should use DataNodeLayoutVersion instead of NameNodeLayoutVersion
Date Fri, 28 Feb 2014 23:06:19 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916548#comment-13916548
] 

Tsz Wo (Nicholas), SZE commented on HDFS-6034:
----------------------------------------------

{code}
+    // verify registration ID
+    final String id = nodeReg.getRegistrationID();
+    final String expectedID = namesystem.getRegistrationID();
+    if (!expectedID.equals(id)) {
+      LOG.warn("Registration IDs mismatched: the "
+          + nodeReg.getClass().getSimpleName() + " ID is " + id
+          + " but the expected ID is " + expectedID);
+       throw new UnregisteredNodeException(nodeReg);
{code}


> 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)

Mime
View raw message