hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liyin Liang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (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
Date Wed, 20 Jul 2011 07:59:57 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Liyin Liang updated MAPREDUCE-2714:
-----------------------------------

    Attachment: 2714-1.diff

> 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

        

Mime
View raw message