[
https://issues.apache.org/jira/browse/HADOOP-16792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017943#comment-17017943
]
Gabor Bota edited comment on HADOOP-16792 at 1/17/20 12:42 PM:
---------------------------------------------------------------
Yes, sure.
I added my review on the PR.
was (Author: gabor.bota):
Yes, sure.
> Let s3 clients configure request timeout
> ----------------------------------------
>
> Key: HADOOP-16792
> URL: https://issues.apache.org/jira/browse/HADOOP-16792
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Mustafa Iman
> Assignee: Mustafa Iman
> Priority: Major
>
> S3 does not guarantee latency. Every once in a while a request may straggle
> and drive latency up for the greater procedure. In these cases, simply
> timing-out the individual request is beneficial so that the client
> application can retry. The retry tends to complete faster than the original
> straggling request most of the time. Others experienced this issue too:
> [https://arxiv.org/pdf/1911.11727.pdf] .
> S3 configuration already provides timeout facility via
> `ClientConfiguration#setTimeout`. Exposing this configuration is beneficial
> for latency sensitive applications. S3 client configuration is shared with
> DynamoDB client which is also affected from unreliable worst case latency.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
