You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "André Kelpe (JIRA)" <ji...@apache.org> on 2013/08/29 10:29:51 UTC

[jira] [Resolved] (HADOOP-9914) nodes overview should use FQDNs

     [ https://issues.apache.org/jira/browse/HADOOP-9914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

André Kelpe resolved HADOOP-9914.
---------------------------------

    Resolution: Invalid
    
> nodes overview should use FQDNs
> -------------------------------
>
>                 Key: HADOOP-9914
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9914
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.1.0-beta
>            Reporter: André Kelpe
>
> I am running a hadoop cluster in a bunch of VMs on my local machine and I am using avahi/zeroconf to do local name resolution (this is to avoid having to fiddle with my /etc/hosts file). 
> The resourcemanager has an overview page, with links to all the nodemanager web-interfaces. The links do not work with zeroconf, due to the fact that the links are not including the domain part. zeroconf domains look like this "hadoop1.local", but the web-interface uses "hadoop1", which will not resolve.
> In hadoop 1.x all web-interfaces were using FQDN, meaning using avahi/zeroconf for name resolution was no problem. The same should be possible in hadoop 2.x.
> I am still beginning to work with hadoop 2.x, so there might be other parts, having the same problem, but I am not yet aware of any. If I find more of these, I will update this bug.

--
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