Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 5 Jun 2015 18:07:00 +0000 (UTC)
From: "Duo Xu (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12835782.1433525499000.5016.1433527620651@Atlassian.JIRA>
In-Reply-To: <JIRA.12835782.1433525499000@Atlassian.JIRA>
References: <JIRA.12835782.1433525499000@Atlassian.JIRA>
 <JIRA.12835782.1433525499718@arcas>
Subject: [jira] [Work started] (HADOOP-12067) Add exponential retry when
 copyblob is throttled by Azure storage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Work on HADOOP-12067 started by Duo Xu.
---------------------------------------
> Add exponential retry when copyblob is throttled by Azure storage
> -----------------------------------------------------------------
>
>                 Key: HADOOP-12067
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12067
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 2.7.0
>            Reporter: Duo Xu
>            Assignee: Duo Xu
>
> HADOOP-11693 passes exponential retry policy to Azure storage SDK when Azure storage throttling happens. However, when I looked at the source code of Azure storage SDK. Storage exceptions such as throttling exception are non-retryable.
> I would like to add retry in WASB driver instead of depending on Azure storage SDK to make sure retry happens when Azure storage throttling fires.


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