hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6478) Add an option to skip cleanupJob stage or ignore cleanup failure during commitJob().
Date Wed, 16 Sep 2015 11:40:46 GMT

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

Hadoop QA commented on MAPREDUCE-6478:
--------------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  16m 46s | Pre-patch trunk compilation is healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any @author tags.
|
| {color:red}-1{color} | tests included |   0m  0s | The patch doesn't appear to include any
new or modified tests.  Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. |
| {color:green}+1{color} | javac |   7m 54s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |  10m  5s | There were no new javadoc warning messages.
|
| {color:green}+1{color} | release audit |   0m 24s | The applied patch does not increase
the total number of release audit warnings. |
| {color:green}+1{color} | checkstyle |   0m 49s | There were no new checkstyle issues. |
| {color:green}+1{color} | whitespace |   0m  0s | The patch has no lines that end in whitespace.
|
| {color:green}+1{color} | install |   1m 30s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 33s | The patch built with eclipse:eclipse.
|
| {color:green}+1{color} | findbugs |   1m 26s | The patch does not introduce any new Findbugs
(version 3.0.0) warnings. |
| {color:green}+1{color} | mapreduce tests |   1m 45s | Tests passed in hadoop-mapreduce-client-core.
|
| | |  41m 17s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12756222/MAPREDUCE-6478-v1.1.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / bf2f2b4 |
| hadoop-mapreduce-client-core test log | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5994/artifact/patchprocess/testrun_hadoop-mapreduce-client-core.txt
|
| Test Results | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5994/testReport/
|
| Java | 1.7.0_55 |
| uname | Linux asf908.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep
3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5994/console |


This message was automatically generated.

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

Mime
View raw message