You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Gaurav Kanade (JIRA)" <ji...@apache.org> on 2016/12/13 00:35:58 UTC

[jira] [Updated] (HADOOP-13831) Correct check for error code to detect Azure Storage Throttling and provide retries

     [ https://issues.apache.org/jira/browse/HADOOP-13831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gaurav Kanade updated HADOOP-13831:
-----------------------------------
    Attachment: HADOOP-13831.001.patch

> 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
>         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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org