[
https://issues.apache.org/jira/browse/MAPREDUCE-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228855#comment-13228855
]
Hadoop QA commented on MAPREDUCE-4006:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12518268/MR4006.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 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 passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2044//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2044//console
This message is automatically generated.
> history server container log web UI sometimes combines stderr/stdout/syslog
> contents together
> ---------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4006
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4006
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver, mrv2
> Affects Versions: 0.23.2
> Reporter: Jason Lowe
> Assignee: Siddharth Seth
> Attachments: MR4006.txt
>
>
> When log aggregation is enabled, going to the job history server UI for the
> AM container log can show the log contents combined together. Examples I've
> seen are portions of the syslog contents appended to either the stderr or
> stdout contents. The log corruption does not occur when using the mapred job
> -logs command, so this appears to be something specific to the history server
> web UI.
--
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
