You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Liyin Liang (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/11 07:26:51 UTC

[jira] [Resolved] (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:all-tabpanel ]

Liyin Liang resolved MAPREDUCE-2714.
------------------------------------

    Resolution: Duplicate
    
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira