[
https://issues.apache.org/jira/browse/HADOOP-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283733#comment-13283733
]
Ivan Mitic commented on HADOOP-8414:
------------------------------------
Thanks for the pointers Daryn! After looking more into this, I came to the
following:
InetAddress.getByName("127.0.0.1").getHostName() == localhost (on Linux)
InetAddress.getByName("127.0.0.1").getHostName() == 127.0.0.1 (on Windows)
Going further, namenode's default filesystem URI is created using the above
host name, and this URI is later used for DFS path resolution.
>From looking at the documentation for InetAddress.getHostName(), it is
>supposed to perform a reverse DNS lookup of the address. For some reason, this
>does not work well for 127.0.0.1 in Java under Windows. I tried a few other IP
>addresses, and getByName(IP).getHostName() worked fine.
Do you maybe have other suggestions/alternatives we can use to address the
problem?
> Address problems related to localhost resolving to 127.0.0.1 on Windows
> -----------------------------------------------------------------------
>
> Key: HADOOP-8414
> URL: https://issues.apache.org/jira/browse/HADOOP-8414
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs, test
> Affects Versions: 1.0.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8414-branch-1-win.patch,
> HADOOP-8414-branch-1-win.patch
>
>
> Localhost resolves to 127.0.0.1 on Windows and that causes the following
> tests to fail:
> - TestHarFileSystem
> - TestCLI
> - TestSaslRPC
> This Jira tracks fixing these tests and other possible places that have
> similar issue.
--
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
