You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Robert Chansler (JIRA)" <ji...@apache.org> on 2008/08/08 20:13:44 UTC
[jira] Updated: (HADOOP-3613) UnknownHostException if the system
can't determine its own name and you go
DNS.getIPs("name-of-an-unknown-interface");
[ https://issues.apache.org/jira/browse/HADOOP-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Chansler updated HADOOP-3613:
------------------------------------
Component/s: dfs
> UnknownHostException if the system can't determine its own name and you go DNS.getIPs("name-of-an-unknown-interface");
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3613
> URL: https://issues.apache.org/jira/browse/HADOOP-3613
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Reporter: Steve Loughran
>
> If you give an interface that doesnt exist, DNS.getIPs falls back to
> InetAddress.getLocalHost().getHostAddress()
> But there's an assumption there: that InetAddress.getLocalHost(). is valid. If it doesnt resolve properly, you get an UnknownHostException
> java.net.UnknownHostException: k2: k2
> at java.net.InetAddress.getLocalHost(InetAddress.java:1353)
> at org.apache.hadoop.net.DNS.getIPs(DNS.java:96)
> at org.apache.hadoop.net.TestDNS.testIPsOfUnknownInterface(TestDNS.java:73)
> It is possible to catch this and return something else. The big question: what to fall back to? 127.0.0.1 would be an obvious choice
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.