hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-870) Clean up the job Retire code
Date Fri, 21 Aug 2009 11:01:14 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745899#action_12745899
] 

Devaraj Das commented on MAPREDUCE-870:
---------------------------------------

+1

> Clean up the job Retire code
> ----------------------------
>
>                 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
>         Attachments: 870_v1.patch, 870_v2.patch, 870_v3.patch
>
>
> 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.


Mime
View raw message