[
https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053006#comment-13053006
]
Hadoop QA commented on HDFS-2086:
---------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12483384/HDFS-2086.4.patch
against trunk revision 1138262.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 4 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/813//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/813//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/813//console
This message is automatically generated.
> If the include hosts list contains host name, after restarting namenode,
> datanodes registrant is denied
> --------------------------------------------------------------------------------------------------------
>
> Key: HDFS-2086
> URL: https://issues.apache.org/jira/browse/HDFS-2086
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Tanping Wang
> Assignee: Tanping Wang
> Fix For: 0.23.0
>
> Attachments: HDFS-2086.2.patch, HDFS-2086.3.patch, HDFS-2086.4.patch,
> HDFS-2086.patch
>
>
> As the title describes the problem: if the include host list contains host
> name, after restarting namenodes, the datanodes registrant is denied by
> namenodes. This is because after namenode is restarted, the still alive data
> node will try to register itself with the namenode and it identifies itself
> with its *IP address*. However, namenode only allows all the hosts in its
> hosts list to registrant and all of them are hostnames. So namenode would
> deny the datanode registration.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
