[
https://issues.apache.org/jira/browse/HADOOP-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281860#comment-13281860
]
Ivan Mitic commented on HADOOP-8414:
------------------------------------
bq. If however #2 is also returning localhost as expected, then it means
there's probably something wrong in FsShell or DistributedFileSystem's handling
of the URI.
Oh, sorry for not being clear, below is the output:
InetAddress.getByName(null).getHostName() == localhost
InetAddress.getByName(null).getCanonicalHostName() == 127.0.0.1
InetAddress.getByName("localhost").getHostName() == localhost
InetAddress.getByName("localhost").getCanonicalHostName() == 127.0.0.1
new InetSocketAddress("localhost", 8000).getHostName() == localhost
PS. thanks for the tip.
> 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