hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8154) DNS#getIPs shouldn't silently return the local host IP for bogus interface names
Date Fri, 09 Mar 2012 00:11:58 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225700#comment-13225700

Eli Collins commented on HADOOP-8154:

bq. Under what circumstances would the following code trigger?

When enumerating local interfaces the JVM creates a dummy socket, if socket(2) fails it throws
a SocketException, so not likely in practice. In HADOOP-8156 I've plumbed that up to the caller,
if you don't mind I'll leave that case alone here since it's a separate code path.
> DNS#getIPs shouldn't silently return the local host IP for bogus interface names
> --------------------------------------------------------------------------------
>                 Key: HADOOP-8154
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8154
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: hadoop-8154.txt
> DNS#getIPs silently returns the local host IP for bogus interface names. In this case
let's throw an UnknownHostException. This is technically an incompatbile change. I suspect
the current behavior was origininally introduced so the interface name "default" works w/o
explicitly checking for it. It may also be used in cases where someone is using a shared config
file and an option like "dfs.datanode.dns.interface" or "hbase.master.dns.interface" and eg
interface "eth3" that some hosts don't have, though I think silently ignorning this is the
wrong behavior (those hosts should be configured to use a different interface).

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


View raw message