[
https://issues.apache.org/jira/browse/HADOOP-13831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745277#comment-15745277
]
Steve Loughran commented on HADOOP-13831:
-----------------------------------------
# assigned to you
# Because yetus/jenkins doesn't test them, we try to keep a strict policy of
"submitter must attest to having passed tests for the relevant object store", :
https://wiki.apache.org/hadoop/HowToContribute#Submitting_patches_against_object_stores_such_as_Amazon_S3.2C_OpenStack_Swift_and_Microsoft_Azure
. Can you confirm that you have done so.
> 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
> 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]
