[
https://issues.apache.org/jira/browse/MAPREDUCE-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245541#comment-13245541
]
Bhallamudi Venkata Siva Kamesh commented on MAPREDUCE-4059:
-----------------------------------------------------------
Hi Robert,
if count is null, I think assigning count as jobs.size() seems a good option
for me. If so, I think we won't have any overflows and can eliminate the
following piece of the code.
{code:xml}
if(end < 0) { //due to overflow
end = Long.MAX_VALUE;
}
{code}
Any comments?
> The history server should have a separate pluggable storage/query interface
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-4059
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4059
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Affects Versions: 0.24.0, 0.23.3
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Attachments: MR-4059.txt, MR-4059.txt, MR-4059.txt, MR-4059.txt
>
>
> The history server currently caches all parsed jobs in RAM. These jobs can
> be very large because of counters. It would be nice to have a pluggable
> interface for the cacheing and querying of the cached data so that we can
> play around with different implementations. Also just for cleanness of the
> code it would be nice to split the very large JobHistoryServer.java into a
> few smaller ones that are more understandable and readable.
--
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
