You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2012/06/26 18:28:45 UTC

[jira] [Updated] (MAPREDUCE-4283) Display tail of aggregated logs by default

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe updated MAPREDUCE-4283:
----------------------------------

    Attachment: MAPREDUCE-4283.patch

Patch to add start/end parameters to aggregated log pages and uses start=-4K by default.  Manually tested by running a sleep job on a single-node cluster with compressed aggregated logs enabled and examining the logs from the history server web pages.
                
> 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
>         Attachments: 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