[
https://issues.apache.org/jira/browse/MAPREDUCE-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414143#comment-13414143
]
Hadoop QA commented on MAPREDUCE-4283:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12536472/MAPREDUCE-4283.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+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
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2590//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2590//console
This message is automatically generated.
> Display tail of aggregated logs by default
> ------------------------------------------
>
> Key: MAPREDUCE-4283
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4283
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobhistoryserver, mrv2
> Affects Versions: 0.23.3, 2.0.1-alpha
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: MAPREDUCE-4283.patch, MAPREDUCE-4283.patch,
> MAPREDUCE-4283.patch
>
>
> Similar to the manner in which the nodemanager webUI displays container logs,
> it would be very useful if the historyserver showed the trailing 4K or so of
> the aggregated logs with a link to see the full log.
> When debugging issues the relevant errors are usually at the end of the log,
> so showing just the last few K can enable quick diagnosis without waiting for
> what can be many megabytes of log data to download.
--
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
