[
https://issues.apache.org/jira/browse/HADOOP-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281593#comment-13281593
]
Daryn Sharp commented on HADOOP-8414:
-------------------------------------
bq. For InetAddress.getByName(), the two actually return different values,
"localhost" and "127.0.0.1", respectively.
Good, that is exactly what I would expect! However this makes it even more odd
that {{new InetSocketAddress("localhost", port).getHostName()}} on windows will
return {{127.0.0.1}} instead of {{localhost}}... The {{InetSocketAddress}}
ctor is supposed to call {{InetAddress.getByName(host)}} and then
{{InetSocketAddress#getHostName()}} delegates to {{InetAddress#getHostName()}}.
I would expect {{InetAddress.getByName(hostname)}} to behave similarly for
{{localhost}} and {{null}} as the given hostname.
Could you please do the same testing with
{{InetAddress.getByName("localhost")}} to ensure that something else isn't
botching the hostname to {{127.0.0.1}}?
> 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
