[
https://issues.apache.org/jira/browse/MAPREDUCE-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharad Agarwal updated MAPREDUCE-870:
-------------------------------------
Description:
Currently completed job's full data structures are kept in memory based on
mapred.jobtracker.completeuserjobs.maximum,
mapred.jobtracker.retirejob.interval.min, mapred.jobtracker.retirejob.interval
and mapred.jobtracker.retirejob.check settings. These controls are not much
useful now since MAPREDUCE-817 introduced a cache for keeping just the very
basic info of the completed job. These settings should be removed and the job
should be purged as soon as the history files are available in HDFS.
Going forward, clients can read the history files if they need to drill down
into more information (MAPREDUCE-864).
> Purge the completed job from memory as soon as the history file is copied in
> to HDFS
> ------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-870
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-870
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Reporter: Sharad Agarwal
> Assignee: Sharad Agarwal
>
> Currently completed job's full data structures are kept in memory based on
> mapred.jobtracker.completeuserjobs.maximum,
> mapred.jobtracker.retirejob.interval.min,
> mapred.jobtracker.retirejob.interval and mapred.jobtracker.retirejob.check
> settings. These controls are not much useful now since MAPREDUCE-817
> introduced a cache for keeping just the very basic info of the completed job.
> These settings should be removed and the job should be purged as soon as the
> history files are available in HDFS.
> Going forward, clients can read the history files if they need to drill down
> into more information (MAPREDUCE-864).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
