[
https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054147#comment-13054147
]
Hudson commented on HDFS-2086:
------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #755 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/755/])
HDFS-2086. If the include hosts list contains host names, after restarting
namenode, data nodes registration is denied. Contributed by Tanping Wang.
tanping :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1139090
Files :
*
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* /hadoop/common/trunk/hdfs/CHANGES.txt
*
/hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/server/namenode/TestStartup.java
> 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.5.patch, HDFS-2086.6.patch, HDFS-2086.7.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
