[
https://issues.apache.org/jira/browse/MAPREDUCE-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415228#comment-13415228
]
Robert Joseph Evans commented on MAPREDUCE-4283:
------------------------------------------------
I like the changes, but I have one new nit with it. Inside
getContainerLogsReader I don't like using toString for the comparison of the
key and the containerId. I know that is what has to ultimately happen, but I
would prefer to see that code move up into LogKey. I would like to see a
method like boolean LogKey.isFor(ContainerId). LogKey holds the code that
knows how to initialize itself from a ContainerId, I would prefer to have it
also hold the code so it knows how to check to see if they are the same.
> 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.1.0-alpha
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: MAPREDUCE-4283.patch, 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
