[ https://issues.apache.org/jira/browse/HADOOP-12334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969839#comment-14969839 ]
Hudson commented on HADOOP-12334: --------------------------------- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #570 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/570/]) HADOOP-12334. Change Mode Of Copy Operation of HBase WAL Archiving to (cnauroth: rev 47641fcbc9c41f4a338d8899501e4a310d2e81ad) * hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/AzureNativeFileSystemStore.java * hadoop-common-project/hadoop-common/CHANGES.txt > 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 > Fix For: 2.8.0 > > Attachments: HADOOP-12334.01.patch, HADOOP-12334.02.patch, > HADOOP-12334.03.patch, HADOOP-12334.04.patch, HADOOP-12334.05.patch, > HADOOP-12334.06.patch, HADOOP-12334.07.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)