[
https://issues.apache.org/jira/browse/HADOOP-13831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752529#comment-15752529
]
Hudson commented on HADOOP-13831:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11002 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11002/])
HADOOP-13831. Correct check for error code to detect Azure Storage (liuml07:
rev f92913c35bfda0d565606f9fb9a301ddd4105fd8)
* (edit)
hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/AzureNativeFileSystemStore.java
> Correct check for error code to detect Azure Storage Throttling and provide
> retries
> -----------------------------------------------------------------------------------
>
> Key: HADOOP-13831
> URL: https://issues.apache.org/jira/browse/HADOOP-13831
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure
> Affects Versions: 2.7.3
> Reporter: Gaurav Kanade
> Assignee: Gaurav Kanade
> Fix For: 2.9.0, 3.0.0-alpha2
>
> Attachments: HADOOP-13831.001.patch
>
>
> Azure Storage throttling affects HBase operations such as archiving old
> WALS and others. In such cases the storage driver needs to detect and handle
> the exception. We put in this logic to do the retries however the condition
> to check for the exception is not always met due to inconsistency in which
> the manner the error code is passed back. Instead the retry logic should
> check for http status code (503) which is more reliable and consistent check
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
