Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <1343213117.1249649295048.JavaMail.jira@brutus>
Date: Fri, 7 Aug 2009 05:48:15 -0700 (PDT)
From: "Amar Kamat (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Reopened: (MAPREDUCE-757) JobConf will not be deleted from
 the logs folder if job retires from finalizeJob()
In-Reply-To: <826761560.1247546595151.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Amar Kamat reopened MAPREDUCE-757:
----------------------------------


> JobConf will not be deleted from the logs folder if job retires from finalizeJob()
> ----------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-757
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-757
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>         Attachments: MAPREDUCE-757-v1.0.patch, MAPREDUCE-757-v2.0-branch-0.20.patch, MAPREDUCE-757-v2.0.patch
>
>
> MAPREDUCE-130 fixed the case where the job is retired from the retire jobs thread. But jobs can also retire when the num-job-per-user limit is exceeded. In such cases the conf file will not be deleted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.