hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9520) _HOST doesn't resolve to bound interface
Date Tue, 30 Apr 2013 17:58:18 GMT

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

Daryn Sharp commented on HADOOP-9520:

_HOST on the server will use the canonical hostname of the host which is usually the first
interface.  While using _HOST in a principal within the client's config is ok, the principal
in the server's config should use the exact hostname on multi-interface hosts.
> _HOST doesn't resolve to bound interface
> ----------------------------------------
>                 Key: HADOOP-9520
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9520
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.0.4-alpha
>            Reporter: Allen Wittenauer
> _HOST appears to ignore bound interfaces.  For example, if a host has two interfaces
such that:
> nic0 = gethostname()
> nic1 = someothername
> and then I configure the namenode or resource manager to use someothername:####, the
system still treats _HOST = nic0.  This is especially harmful for Kerberos principals.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message