[
https://issues.apache.org/jira/browse/HADOOP-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-19045:
------------------------------------
Description:
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.
was: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
> S3A: pass request timeouts down to sdk clients
> ----------------------------------------------
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
