Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 18 Sep 2015 17:37:04 +0000 (UTC)
From: "Wangda Tan (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12864386.1442355292000.14152.1442597824403@Atlassian.JIRA>
In-Reply-To: <JIRA.12864386.1442355292000@Atlassian.JIRA>
References: <JIRA.12864386.1442355292000@Atlassian.JIRA>
 <JIRA.12864386.1442355292742@arcas>
Subject: [jira] [Updated] (MAPREDUCE-6478) Add an option to skip cleanupJob
 stage or ignore cleanup failure during commitJob().
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Wangda Tan updated MAPREDUCE-6478:
----------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 2.8.0
           Status: Resolved  (was: Patch Available)

Committed to trunk/branch-2, thanks [~djp]!

> Add an option to skip cleanupJob stage or ignore cleanup failure during commitJob().
> ------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6478
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6478
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Junping Du
>            Assignee: Junping Du
>             Fix For: 2.8.0
>
>         Attachments: MAPREDUCE-6478-v1.1.patch, MAPREDUCE-6478-v1.patch
>
>
> In some of our test cases for MR on public cloud scenario, a very big MR job with hundreds or thousands of reducers cannot finish successfully because of Job Cleanup failures which is caused by different scale/performance impact for File System on the cloud (like AzureFS) which replacing HDFS's deletion for whole directory with REST API calls on deleting each sub-directories recursively. Even it get successfully, that could take much longer time (hours) which is not necessary and waste time/resources especially in public cloud scenario. 
> In these scenarios, some failures of cleanupJob can be ignored or user choose to skip cleanupJob() completely make more sense. This is because making whole job finish successfully with side effect of wasting some user spaces is much better as user's jobs are usually comes and goes in public cloud, so have choices to tolerant some temporary files exists with get rid of big job re-run (or saving job's running time) is quite effective in time/resource cost. 
> We should allow user to have this option (ignore failure or skip job cleanup stage completely) especially when user know the cleanup failure is not due to HDFS abnormal status but other FS' different performance trade-off.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)