[
https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668300#action_12668300
]
Amar Kamat commented on HADOOP-5083:
------------------------------------
Dhruba, in this issue we are not purging jobs based on the memory usage. Here
the jobs are purged as soon as they exceed _some_ amount of time in the
jobtracker which by default is 1 min. There is another process that takes care
of serving/displaying completed job info. HADOOP-4766 was opened to address
what you want. Since completed jobs will no longer remain in the memory, there
is no memory management required.
> 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.
