You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Liyin Liang (JIRA)" <ji...@apache.org> on 2011/07/20 10:02:57 UTC
[jira] [Commented] (MAPREDUCE-2714) When a job is retired by the
same user's another job, its jobconf file is not deleted from the log
directory of the JobTracker
[ https://issues.apache.org/jira/browse/MAPREDUCE-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068206#comment-13068206 ]
Liyin Liang commented on MAPREDUCE-2714:
----------------------------------------
Attaching a patch for 0.20 branch.
> When a job is retired by the same user's another job, its jobconf file is not deleted from the log directory of the JobTracker
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2714
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2714
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.20.1, 0.20.2
> Reporter: Liyin Liang
> Assignee: Liyin Liang
> Attachments: 2714-1.diff
>
>
> After MAPREDUCE-130, the job's conf copy will be deleted from the log directory of the JobTracker when the job is retired. However, it just works if the job is retired by _RetireJobs_ thread of JobTracker. If a job is retired by the same user's another job, its conf copy will not be deleted. This kind of retire happens in _JobTracker::finalizeJob(job)_, when JobTracker maintains more than _MAX_COMPLETE_USER_JOBS_IN_MEMORY_ jobs information in memory for a given user.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira