[
https://issues.apache.org/jira/browse/MAPREDUCE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190021#comment-13190021
]
Ahmed Radwan commented on MAPREDUCE-3436:
-----------------------------------------
@Siddarth Thanks for our offline chat yesterday. I'll summarize my
understanding and please correct me if I am wrong. I think we are speaking
about two separate issues:
Issue1: When the user explicitly set yarn.resourcemanager.address and
mapreduce.jobhistory.address, the jobhistory link is broken (without the
patch), the patch basically avoids the need to explicitly set
mapreduce.jobhistory.webapp.address. This issue doesn't exist in the single
node case because all services run on the single node.
Issue2: If the user doesn't explicitly set yarn.resourcemanager.address, then
all links (AM tracking url and jobhistory url) are broken. This issue even
exists on a single node setup as you mentioned (if the user tries to connect
from another node).
However, I am not sure if Issue2 is a bug or not: For a single node setup, if
yarn.resourcemanager.address is not set, the user can still play with the web
ui if connecting from the same single node, and all links will work. On a real
cluster (multinode), it is expected/required to set the
yarn.resourcemanager.address and mapreduce.jobhistory.address for the cluster
to function, and so, with the patch, all links will also work.
> 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
