[jira] [Commented] (HADOOP-12334) Change Mode Of Copy Operation of HBase WAL Archiving to bypass Azure Storage Throttling after retries

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on HADOOP-12334:
------------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  17m 58s | 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 |  10m  5s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |  11m 51s | 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 24s | There were no new checkstyle issues. |
| {color:green}+1{color} | whitespace |   0m  1s | The patch has no lines that end in whitespace. |
| {color:green}+1{color} | install |   1m 39s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 39s | The patch built with eclipse:eclipse. |
| {color:green}+1{color} | findbugs |   0m 56s | The patch does not introduce any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | tools/hadoop tests |   1m 24s | Tests passed in hadoop-azure. |
| | |  45m 24s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12753389/HADOOP-12334.05.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 826ae1c |
| hadoop-azure test log | https://builds.apache.org/job/PreCommit-HADOOP-Build/7564/artifact/patchprocess/testrun_hadoop-azure.txt |
| Test Results | https://builds.apache.org/job/PreCommit-HADOOP-Build/7564/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/7564/console |


This message was automatically generated.

> Change Mode Of Copy Operation of HBase WAL Archiving to bypass Azure Storage Throttling after retries
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-12334
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12334
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: tools
>            Reporter: Gaurav Kanade
>            Assignee: Gaurav Kanade
>         Attachments: HADOOP-12334.01.patch, HADOOP-12334.02.patch, HADOOP-12334.03.patch, HADOOP-12334.04.patch, HADOOP-12334.05.patch
>
>
> HADOOP-11693 mitigated the problem of HMaster aborting regionserver due to Azure Storage Throttling event during HBase WAL archival. The way this was achieved was by applying an intensive exponential retry when throttling occurred.
> As a second level of mitigation we will change the mode of copy operation if the operation fails even after all retries -i.e. we will do a client side copy of the blob and then copy it back to destination. This operation will not be subject to throttling and hence should provide a stronger mitigation. However it is more expensive, hence we do it only in the case we fail after all retries



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