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 "hawin (JIRA)" <ji...@apache.org> on 2014/04/02 21:36:15 UTC

[jira] [Resolved] (HADOOP-10403) Hadoop2.2 is not fully transfer hostname to IP address on WEB UI

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

hawin resolved HADOOP-10403.
----------------------------

    Resolution: Done

> Hadoop2.2 is not fully transfer hostname to IP address on WEB UI
> ----------------------------------------------------------------
>
>                 Key: HADOOP-10403
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10403
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf, fs, util
>    Affects Versions: 2.2.0
>         Environment: OS: Linux 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> master: hostname1
> slave1: hostname2
> slave2: hostname3
>            Reporter: hawin
>              Labels: patch
>
> I could not get access when I was trying to click links which are include hostname in the URL.
> For example: 
> My master ip address is 192.168.1.110 and hostname is hostname1
> http://192.168.1.110:50070/ works fine
> but http://hostname1:50070/ does not work. 
> My slave servers also have the same issues. some links only display http://hostname:port.  and some links used IP address replace of hostname.
> I can ping hostname1, hostname2 and hostname3 and also ssh slave servers without password from master server. 
> ********************************************************************
> cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 192.168.1.110 hostname1
> 192.168.1.111 hostname2
> 192.168.1.112 hostname3
> *********************************************************************
> Please help me to check this issue.  I don't know whether I am missing some configuration.  Your hands will be appreciated. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)