hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-15347) S3ARetryPolicy to handle AWS 500 responses/error code TooBusyException with the throttle backoff policy
Date Wed, 28 Mar 2018 10:29:00 GMT

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

Steve Loughran updated HADOOP-15347:
------------------------------------
    Summary: S3ARetryPolicy to handle AWS 500 responses/error code TooBusyException with the
throttle backoff policy  (was: S3ARetryPolicy to handle AWS 500 responses with the throttle
backoff policy)

> S3ARetryPolicy to handle AWS 500 responses/error code TooBusyException with the throttle
backoff policy
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-15347
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15347
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.1.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> FLINK-9061 implies that some 500 responses are caused by server-side overload of some
form. 
> That means they should really have the throttle retry policy applied, not the connectivity
one



--
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


Mime
View raw message