[
https://issues.apache.org/jira/browse/HDFS-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418663#comment-13418663
]
Jason Lowe commented on HDFS-3688:
----------------------------------
When the datanode registers with the namenode, the namenode bashes the
datanode's provided hostname with an IP address and sends this new registration
object back to the datanode, which proceeds to bash over its name with the IP
address. If the datanode ever re-registers, it uses the "updated" hostname
(now IP address) when registering, and the hostname for the datanode is lost.
This appears to only affect 0.23, since branch-2 and trunk have separate fields
for tracking the datanode hostname vs. IP address, so the hostname isn't
clobbered. See changes such as HDFS-3171, HDFS-3144, and HDFS-3164.
> Namenode loses datanode hostname if datanode re-registers
> ---------------------------------------------------------
>
> Key: HDFS-3688
> URL: https://issues.apache.org/jira/browse/HDFS-3688
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node
> Affects Versions: 0.23.3
> Reporter: Jason Lowe
>
> If a datanode ever re-registers with the namenode (e.g.: namenode restart,
> temporary network cut, etc.) then the datanode ends up registering with an IP
> address as the datanode name rather than the hostname.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
