[jira] [Resolved] (HADOOP-18927) S3ARetryHandler to treat SocketExceptions as connectivity failures

["Steve Loughran (Jira)" <ji...@apache.org>]

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

Steve Loughran resolved HADOOP-18927.
-------------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed

> S3ARetryHandler to treat SocketExceptions as connectivity failures
> ------------------------------------------------------------------
>
>                 Key: HADOOP-18927
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18927
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.3.6
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>             Fix For: 3.4.0
>
>
> i've got a v1 sdk stack trace where a TCP connection reset is breaking a large upload. that should be recoverable with retries.
> {code}
> com.amazonaws.SdkClientException: Unable to execute HTTP request: Connection reset by peer: Unable to execute HTTP request: Connection reset by peer at...
> {code}
> proposed:
> * S3ARetryPolicy to map SocketException to connectivity failure
> * See if we can create a test for this, ideally under the aws sdk.
> I'm now unsure about how well we handle these io problems...a quick experiment with the 3.3.5 release shows that the retry policy retries on whatever exception chain has an unknown host for the endpoint. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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