You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2024/07/08 15:58:00 UTC
[jira] [Updated] (HADOOP-19221) S3A: retry on AWS 400 Response +ErrorCode RequestTimeout
[ https://issues.apache.org/jira/browse/HADOOP-19221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-19221:
------------------------------------
Summary: S3A: retry on AWS 400 Response +ErrorCode RequestTimeout (was: S3a: retry on 400 +ErrorCode RequestTimeout)
> S3A: retry on AWS 400 Response +ErrorCode RequestTimeout
> --------------------------------------------------------
>
> Key: HADOOP-19221
> URL: https://issues.apache.org/jira/browse/HADOOP-19221
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Priority: Minor
>
> if a slow block update takes too long then the connection is broken s3 side with an error message, as a 400 response
> {code}
> Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. (Service: Amazon S3; Status Code: 400; Error Code: RequestTimeout; Request ID:; S3 Extended Request ID:
> {code}
> This is recoverable and should be treated as such, either using the normal exception policy or maybe even throttlePolicy
--
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