[ https://issues.apache.org/jira/browse/MAPREDUCE-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332541#comment-16332541 ]
Gergo Repas commented on MAPREDUCE-6984: ---------------------------------------- v009: fixed typo, added a new test covering the recovery-enabled scenario, removed the committer implementation dependent tests, and moved my tests to useĀ mapred.output.committer.class to specify the committer. > MR AM to clean up temporary files from previous attempt > ------------------------------------------------------- > > Key: MAPREDUCE-6984 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6984 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: applicationmaster > Affects Versions: 3.0.0-beta1 > Reporter: Gergo Repas > Assignee: Gergo Repas > Priority: Major > Attachments: MAPREDUCE-6984.000.patch, MAPREDUCE-6984.001.patch, > MAPREDUCE-6984.003.patch, MAPREDUCE-6984.004.patch, MAPREDUCE-6984.005.patch, > MAPREDUCE-6984.006.patch, MAPREDUCE-6984.007.patch, MAPREDUCE-6984.008.patch, > MAPREDUCE-6984.009.patch > > > When the MR AM restarts, the > {outputDir}/_temporary/{appAttemptNumber} directory > remains on HDFS, even though this directory is not used during the next > attempt if the restart has been done without recovery. So if recovery is not > used for the AM restart, then the deletion of this directory can be done > earlier (at the start of the next attempt). The benefit is that more free > HDFS space is available for the next attempt. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org