From common-issues-return-150169-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Mar 22 06:17:10 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id ACD64180651 for ; Thu, 22 Mar 2018 06:17:09 +0100 (CET) Received: (qmail 61933 invoked by uid 500); 22 Mar 2018 05:17:04 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 61341 invoked by uid 99); 22 Mar 2018 05:17:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Mar 2018 05:17:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 9526EC051D for ; Thu, 22 Mar 2018 05:17:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 2FHAVsQTCOsa for ; Thu, 22 Mar 2018 05:17:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 5ACEE5F36B for ; Thu, 22 Mar 2018 05:17:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 41AB2E0D76 for ; Thu, 22 Mar 2018 05:17:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 8A65F214D7 for ; Thu, 22 Mar 2018 05:17:00 +0000 (UTC) Date: Thu, 22 Mar 2018 05:17:00 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HADOOP-14381) S3AUtils.translateException to map 503 reponse to => throttling failure MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-14381?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved HADOOP-14381. ---------------------------------------------- Resolution: Duplicate Fix Version/s: (was: 3.1.0) > S3AUtils.translateException to map 503 reponse to =3D> throttling failure > ----------------------------------------------------------------------- > > Key: HADOOP-14381 > URL: https://issues.apache.org/jira/browse/HADOOP-14381 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 2.8.0 > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Major > > When AWS S3 returns "503", it means that the overall set of requests on a= part of an S3 bucket exceeds the permitted limit; the client(s) need to th= rottle back or away for some rebalancing to complete. > The aws SDK retries 3 times on a 503, but then throws it up. Our code doe= sn't do anything with that other than create a generic {{AWSS3IOException}}= . > Proposed > * add a new exception, {{AWSOverloadedException}} > * raise it on a 503 from S3 (& for s3guard, on DDB complaints) > * have it include a link to a wiki page on the topic, as well as the path > * and any other diags > Code talking to S3 may then be able to catch this and choose to react. So= me retry with exponential backoff is the obvious option. Failing, well, tha= t could trigger task reattempts at that part of the query, then job retry = =E2=80=94which will again fail, *unless the number of tasks run in parallel= is reduced* > As this throttling is across all clients talking to the same part of a bu= cket, fixing it is potentially a high level option. We can at least start b= y reporting things better -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org