[
https://issues.apache.org/jira/browse/MAPREDUCE-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229531#comment-13229531
]
Hadoop QA commented on MAPREDUCE-4005:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12518352/MAPREDUCE-4005.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.mapred.TestWritableJobConf
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2052//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2052//console
This message is automatically generated.
> 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
> 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
