Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 5 Dec 2011 19:58:40 +0000 (UTC)
From: =?utf-8?Q?Bruno_Mah=C3=A9_=28Commented=29_=28JIRA=29?= <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <101230715.42148.1323115120053.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1514912238.46357.1321669852702.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3436) jobhistory link may be broken
 depending on the interface it is listening on
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/MAPREDUCE-3436?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
13162985#comment-13162985 ]=20

Bruno Mah=C3=A9 commented on MAPREDUCE-3436:
---------------------------------------

Does that mean a user cannot have this service listen on all interfaces wit=
hout breaking the ui?

But that would also mean the jobhistory link is broken by default, unless i=
ts config is updated by the user to point to the correct ip/hostname.
I also don't understand why other web ui links are able to figure out the r=
ight hostname/ip by themselves without any extra configuration. I haven't h=
ad time to figure out how it's done exactly, but the jobhistory is the only=
 place where such configuration is needed.


               =20
> jobhistory link may be broken depending on the interface it is listening =
on
> -------------------------------------------------------------------------=
--
>
>                 Key: MAPREDUCE-3436
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3436
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, webapps
>    Affects Versions: 0.23.0, 0.23.1
>            Reporter: Bruno Mah=C3=A9
>            Assignee: Ahmed Radwan
>              Labels: bigtop
>         Attachments: MAPREDUCE-3436.patch
>
>
> On the following page : http://<RESOURCE_MANAGER>:8088/cluster/apps
> There are links to the history for each application. None of them can be =
reached since they all point to the ip 0.0.0.0. For instance:
> http://0.0.0.0:8088/proxy/application_1321658790349_0002/jobhistory/job/j=
ob_1321658790349_2_2
> Am I missing something?
> [root@bigtop-fedora-15 ~]# jps
> 9968 ResourceManager
> 1495 NameNode
> 1645 DataNode
> 12935 Jps
> 11140 -- process information unavailable
> 5309 JobHistoryServer
> 10237 NodeManager
> [root@bigtop-fedora-15 ~]# netstat -tlpn | grep 8088
> tcp        0      0 :::8088                     :::*                     =
   LISTEN      9968/java   =20
> For reference, here is my configuration:
> root@bigtop-fedora-15 ~]# cat /etc/yarn/conf/yarn-site.xml=20
> <?xml version=3D"1.0"?>
> <configuration>
> <!-- Site specific YARN configuration properties -->
>    <property>
>       <name>yarn.nodemanager.aux-services</name>
>       <value>mapreduce.shuffle</value>
>     </property>
>     <property>
>       <name>yarn.nodemanager.aux-services.mapreduce.shuffle.class</name>
>       <value>org.apache.hadoop.mapred.ShuffleHandler</value>
>     </property>
>     <property>
>       <name>mapreduce.admin.user.env</name>
>       <value>CLASSPATH=3D/etc/hadoop/conf/*:/usr/lib/hadoop/*:/usr/lib/ha=
doop/lib/*</value>
>     </property>
> </configuration>
> [root@bigtop-fedora-15 ~]# cat /etc/hadoop/conf/hdfs-site.xml=20
> <?xml version=3D"1.0"?>
> <configuration>
>   <property>
>     <name>dfs.replication</name>
>     <value>1</value>
>   </property>
>   <property>
>      <name>dfs.permissions</name>
>      <value>false</value>
>   </property>
>   <property>
>      <!-- specify this so that running 'hadoop namenode -format' formats =
the right dir -->
>      <name>dfs.name.dir</name>
>      <value>/var/lib/hadoop/cache/hadoop/dfs/name</value>
>   </property>
> </configuration>
> [root@bigtop-fedora-15 ~]# cat /etc/hadoop/conf/core-site.xml=20
> <?xml version=3D"1.0"?>
> <configuration>
>   <property>
>     <name>fs.default.name</name>
>     <value>hdfs://localhost:8020</value>
>   </property>
>   <property>
>      <name>hadoop.tmp.dir</name>
>      <value>/var/lib/hadoop/cache/${user.name}</value>
>   </property>
>   <!-- OOZIE proxy user setting -->
>   <property>
>     <name>hadoop.proxyuser.oozie.hosts</name>
>     <value>*</value>
>   </property>
>   <property>
>     <name>hadoop.proxyuser.oozie.groups</name>
>     <value>*</value>
>   </property>
> </configuration>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira