[
https://issues.apache.org/jira/browse/MAPREDUCE-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231968#comment-13231968
]
Hudson commented on MAPREDUCE-4005:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk #1022 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1022/])
MAPREDUCE-4005. Fixes broken AM container logs URL on ResourceManager
Application Info page. (Contributed by Jason Lowe) (Revision 1301691)
Result = SUCCESS
sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1301691
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/dao/AppInfo.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebServicesApps.java
> AM container logs URL is broken for completed apps when log aggregation is
> enabled
> ----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4005
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4005
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.2
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Fix For: 0.23.2
>
> Attachments: MAPREDUCE-4005.patch
>
>
> With log aggregation enabled and yarn.log.server.url pointing to the job
> history server, the AM container logs URL for a completed application fails
> with the error "Cannot get container logs without an app owner". Looking at
> the code in the nodemanager to handle redirects to the log server, it appears
> the AM container log URL is missing a user name for the job. I verified that
> tacking on the app's user name after the AM container log URL reported by the
> RM works.
--
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
