[ https://issues.apache.org/jira/browse/HADOOP-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579522#comment-14579522 ]
Hadoop QA commented on HADOOP-12067: ------------------------------------ \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | pre-patch | 15m 45s | Pre-patch trunk compilation is healthy. | | {color:green}+1{color} | @author | 0m 0s | The patch does not contain any @author tags. | | {color:green}+1{color} | tests included | 0m 0s | The patch appears to include 1 new or modified test files. | | {color:green}+1{color} | javac | 7m 49s | There were no new javac warning messages. | | {color:green}+1{color} | javadoc | 9m 48s | There were no new javadoc warning messages. | | {color:green}+1{color} | release audit | 0m 23s | The applied patch does not increase the total number of release audit warnings. | | {color:red}-1{color} | checkstyle | 0m 21s | The applied patch generated 4 new checkstyle issues (total was 37, now 28). | | {color:red}-1{color} | whitespace | 0m 0s | The patch has 4 line(s) that end in whitespace. Use git apply --whitespace=fix. | | {color:green}+1{color} | install | 1m 33s | mvn install still works. | | {color:green}+1{color} | eclipse:eclipse | 0m 32s | The patch built with eclipse:eclipse. | | {color:green}+1{color} | findbugs | 0m 49s | The patch does not introduce any new Findbugs (version 3.0.0) warnings. | | {color:green}+1{color} | tools/hadoop tests | 1m 11s | Tests passed in hadoop-azure. | | | | 38m 16s | | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12738642/HADOOP-12067.02.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / 3c2397c | | checkstyle | https://builds.apache.org/job/PreCommit-HADOOP-Build/6945/artifact/patchprocess/diffcheckstylehadoop-azure.txt | | whitespace | https://builds.apache.org/job/PreCommit-HADOOP-Build/6945/artifact/patchprocess/whitespace.txt | | hadoop-azure test log | https://builds.apache.org/job/PreCommit-HADOOP-Build/6945/artifact/patchprocess/testrun_hadoop-azure.txt | | Test Results | https://builds.apache.org/job/PreCommit-HADOOP-Build/6945/testReport/ | | Java | 1.7.0_55 | | uname | Linux asf903.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-HADOOP-Build/6945/console | This message was automatically generated. > Add exponential retry when copyblob is throttled by Azure storage > ----------------------------------------------------------------- > > Key: HADOOP-12067 > URL: https://issues.apache.org/jira/browse/HADOOP-12067 > Project: Hadoop Common > Issue Type: Bug > Components: tools > Affects Versions: 2.7.0 > Reporter: Duo Xu > Assignee: Duo Xu > Attachments: HADOOP-12067.01.patch, HADOOP-12067.02.patch > > > HADOOP-11693 passes exponential retry policy to Azure storage SDK when Azure > storage throttling happens. However, when I looked at the source code of > Azure storage SDK. Storage exceptions such as throttling exception are > non-retryable. > I would like to add retry in WASB driver instead of depending on Azure > storage SDK to make sure retry happens when Azure storage throttling fires. -- This message was sent by Atlassian JIRA (v6.3.4#6332)