You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2013/02/22 02:21:12 UTC
[jira] [Commented] (HDFS-4269) DatanodeManager#registerDatanode
rejects all datanode registrations from localhost in single-node developer
setup
[ https://issues.apache.org/jira/browse/HDFS-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583783#comment-13583783 ]
Konstantin Boudnik commented on HDFS-4269:
------------------------------------------
This original "feature" also breaks Linux especially CentOS with its silly way of configuring {{/etc/hosts}}
> DatanodeManager#registerDatanode rejects all datanode registrations from localhost in single-node developer setup
> -----------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-4269
> URL: https://issues.apache.org/jira/browse/HDFS-4269
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0, trunk-win
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Fix For: 3.0.0
>
> Attachments: HDFS-4269.1.patch, HDFS-4269.2.patch, HDFS-4269.3.patch
>
>
> HDFS-3990 is a change that optimized some redundant DNS lookups. As part of that change, {{DatanodeManager#registerDatanode}} now rejects attempts to register a datanode for which the name has not been resolved. Unfortunately, this broke single-node developer setups on Windows, because Windows does not resolve 127.0.0.1 to "localhost".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira