Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 16 Jul 2017 10:19:01 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13087073.1500001198000.257004.1500200341439@Atlassian.JIRA>
In-Reply-To: <JIRA.13087073.1500001198000@Atlassian.JIRA>
References: <JIRA.13087073.1500001198000@Atlassian.JIRA> <JIRA.13087073.1500001198882@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HADOOP-14660) wasb: improve throughput by 34%
 when account limit exceeded
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 16 Jul 2017 10:19:10 -0000


    [ https://issues.apache.org/jira/browse/HADOOP-14660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088874#comment-16088874 ] 

Hadoop QA commented on HADOOP-14660:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} | {color:red} HADOOP-14660 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-14660 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12877462/HADOOP-14660-006.patch |
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/12792/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.


> wasb: improve throughput by 34% when account limit exceeded
> -----------------------------------------------------------
>
>                 Key: HADOOP-14660
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14660
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/azure
>            Reporter: Thomas
>            Assignee: Thomas
>         Attachments: HADOOP-14660-001.patch, HADOOP-14660-002.patch, HADOOP-14660-003.patch, HADOOP-14660-004.patch, HADOOP-14660-005.patch, HADOOP-14660-006.patch
>
>
> Big data workloads frequently exceed the Azure Storage max ingress and egress limits (https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits).  For example, the max ingress limit for a GRS account in the United States is currently 10 Gbps.  When the limit is exceeded, the Azure Storage service fails a percentage of incoming requests, and this causes the client to initiate the retry policy.  The retry policy delays requests by sleeping, but the sleep duration is independent of the client throughput and account limit.  This results in low throughput, due to the high number of failed requests and thrashing causes by the retry policy.
> To fix this, we introduce a client-side throttle which minimizes failed requests and maximizes throughput.  Tests have shown that this improves throughtput by ~34% when the storage account max ingress and/or egress limits are exceeded. 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org