[
https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668379#action_12668379
]
Amar Kamat commented on HADOOP-5083:
------------------------------------
{quote}
currently have deployed a fix for our cluster (pre 0.19) that retires most
completed jobs when the memory usage on the JT reached 90% of the max heap
size. This could be of great help under times of memory pressure on the JT.
This solution is possibly better than setting number of completed jobs in
memory = 0, because doing this will always retire jobs immediately. I would
rather retire jobs during times of high memory pressure on the JT.
{quote}
HADOOP-4766 tried to do the same thing. Plz look at the discussion as to why
jobs should not be retired based on memory usage. HADOOP-4766 can still be used
to address memory issues in 0.19. Thoughts?
> Optionally a separate daemon should serve JobHistory
> ----------------------------------------------------
>
> Key: HADOOP-5083
> URL: https://issues.apache.org/jira/browse/HADOOP-5083
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Arun C Murthy
> Assignee: Amar Kamat
> Attachments: HADOOP-5083-v1.2.patch, HADOOP-5083-v1.9.patch
>
>
> Currently the JobTracker serves the JobHistory to end-users off files
> local-disk/hdfs. While running very large clusters with a large user-base
> might result in lots of traffic for job-history which needlessly taxes the
> JobTracker. The proposal is to have an optional daemon which handles serving
> of job-history requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
