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/02/08 14:20:00 UTC

[jira] [Updated] (HADOOP-19045) HADOOP-19045. S3A: CreateSession Timeout after 10 seconds

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

Steve Loughran updated HADOOP-19045:
------------------------------------
    Summary: HADOOP-19045. S3A: CreateSession Timeout after 10 seconds  (was: S3A: pass request timeouts down to sdk clients)

> HADOOP-19045. S3A: CreateSession Timeout after 10 seconds
> ---------------------------------------------------------
>
>                 Key: HADOOP-19045
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19045
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.4.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.5.0, 3.4.1
>
>
> s3a client timeout settings are getting down to http client, but not sdk timeouts, so you can't have a longer timeout than the default. This surfaces in the inability to tune the timeouts for CreateSession calls even now the latest SDK does pick it up
> The default value of {{fs.s3a.connection.request.timeout}} is now 60s; if an S3 store takes longer than this to return then the operation will be reported by the SDK as a timeout.



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