[
https://issues.apache.org/jira/browse/MAPREDUCE-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123989#comment-15123989
]
Robert Kanter commented on MAPREDUCE-6622:
------------------------------------------
If we add the -1, 0, and >0 for the cleanUp(), make sure to explain the
implications of that in the description.
A few other small things:
# We should change {{if (loadedTasksCacheSize==-1) \{}} to {{if
(loadedTasksCacheSize<=-1) \{}}. Otherwise the user will get an
{{IllegalArgumentException}} when it tries to do the {{CacheBuilder}} stuff.
This way, it will revert to the old behavior, which is nicer.
# Can we call {{lruJobTracker}} something else? {{JobTracker}} is used enough
in Hadoop 1 :)
> Add capability to set JHS job cache to a task-based limit
> ---------------------------------------------------------
>
> Key: MAPREDUCE-6622
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6622
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobhistoryserver
> Affects Versions: 2.7.2
> Reporter: Ray Chiang
> Assignee: Ray Chiang
> Labels: supportability
> Attachments: MAPREDUCE-6622.001.patch
>
>
> When setting the property mapreduce.jobhistory.loadedjobs.cache.size the jobs
> can be of varying size. This is generally not a problem when the jobs sizes
> are uniform or small, but when the job sizes can be very large (say greater
> than 250k tasks), then the JHS heap size can grow tremendously.
> In cases, where multiple jobs are very large, then the JHS can lock up and
> spend all its time in GC. However, since the cache is holding on to all the
> jobs, not much heap space can be freed up.
> By setting a property that sets a cap on the number of tasks allowed in the
> cache and since the total number of tasks loaded is directly proportional to
> the amount of heap used, this should help prevent the JHS from locking up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
