[
https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052244#comment-13052244
]
Tanping Wang commented on HDFS-2086:
------------------------------------
There is a second part of this problem. When namenode checks datanode status by
calling
FSNameSystem#getDatanodeListForReport
The namenode goes over its include hosts list and tries to determine if all the
hosts in the include list are all registrant. If not, the host will be added
into the dead list. In our case, as just mentioned early, after the namenode
restarted, datanode registrants itself with its *IP address*. But the include
list still
contains its *host name*. So the hostname is not recognized by namenode and is
added into the dead list when namenode reports the datanodes status.
> 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
> Fix For: 0.23.0
>
>
> As the tile 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
