Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 17 Oct 2011 17:06:10 +0000 (UTC)
From: "Mahadev konar (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <671608779.1092.1318871170714.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <719916468.23306.1312222209819.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-2762) [MR-279] - Cleanup staging dir
 after job completion
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mahadev konar commented on MAPREDUCE-2762:
------------------------------------------

Yeah had thought abt that. I was trying to keep the MRAppMaster code clean and did not want to inject any code from Jobs in the MRAppMaster. 
As Vinod tells me, the code is already tainted with the uber AM, so I'll go ahead and make the quick fix for cleaning the staging directories.
We'll have to rethink the MRAppMaster code when we do DAG of jobs in the AM.
                
> [MR-279] - Cleanup staging dir after job completion
> ---------------------------------------------------
>
>                 Key: MAPREDUCE-2762
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2762
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Ramya Sunil
>            Assignee: Mahadev konar
>            Priority: Blocker
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2762.patch, MAPREDUCE-2762.patch, MAPREDUCE-2762.patch, MAPREDUCE-2762.patch
>
>
> The files created under the staging dir have to be deleted after job completion. Currently, all job.* files remain forever in the ${yarn.apps.stagingDir}

--
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