[
https://issues.apache.org/jira/browse/HADOOP-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674484#action_12674484
]
Sharad Agarwal commented on HADOOP-5083:
----------------------------------------
I think we should keep the default value of
"mapred.jobtracker.retirejob.interval" as the old value that is 24 hrs. There
are fewer cases which need lower value, those can set it lower. By default
people would expect that they can see jobs in the completed list for some time
after the job is finished. Also task reports won't be accessible in jobclient
for retired jobs.
minor nit:
should we create new UtilsforTests in mapreduce package and write the utilities
related to new api there?
> 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.11.4.patch, HADOOP-5083-v1.11.5.patch,
> HADOOP-5083-v1.2.patch, HADOOP-5083-v1.9.4.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.
