[
https://issues.apache.org/jira/browse/MAPREDUCE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189392#comment-13189392
]
Ahmed Radwan commented on MAPREDUCE-3436:
-----------------------------------------
Thanks Siddarth, I am afraid I am misunderstanding something. To make sure we
are talking about the same issue, and since this issue doesn't exist on a
single node setup, will you be able to test the patch on a multinode setup (2
nodes for instance)? For example: running all services except HS on one node
and HS on the second node. And see if you are seeing the same reported behavior
with and without the patch (i.e. the JobHistory link is broken without the
patch). You'll need to explicitly set mapreduce.jobhistory.address in both
cases.
> 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é
> Assignee: Ahmed Radwan
> Labels: bigtop
> Attachments: MAPREDUCE-3436.patch, MAPREDUCE-3436_rev2.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/job_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
> For reference, here is my configuration:
> root@bigtop-fedora-15 ~]# cat /etc/yarn/conf/yarn-site.xml
> <?xml version="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=/etc/hadoop/conf/*:/usr/lib/hadoop/*:/usr/lib/hadoop/lib/*</value>
> </property>
> </configuration>
> [root@bigtop-fedora-15 ~]# cat /etc/hadoop/conf/hdfs-site.xml
> <?xml version="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
> <?xml version="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 administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
