[
https://issues.apache.org/jira/browse/HADOOP-18759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728994#comment-17728994
]
Steve Loughran commented on HADOOP-18759:
-----------------------------------------
it'd be good if we could collect this in iostats for the current thread
context, and when that is not set, to the fs. knowing there have been lots of
network problems is good to know
> [ABFS}[Backoff-Optimization] Have a Linear retry policy for connection
> timeout failures
> ---------------------------------------------------------------------------------------
>
> Key: HADOOP-18759
> URL: https://issues.apache.org/jira/browse/HADOOP-18759
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.3.4
> Reporter: Anuj Modi
> Assignee: Anuj Modi
> Priority: Major
>
> Today when a request fails with connection timeout, it falls back into the
> loop for exponential retry. Unlike Azure Storage, there are no guarantees of
> success on exponentially retried request or recommendations for ideal retry
> policies for Azure network or any other general failures. Faster failure and
> retry might be more beneficial for such generic connection timeout failures.
> This PR introduces a new Linear Retry Policy which will currently be used
> only for Connection Timeout failures.
> Two types of Linear Backoff calculations will be supported:
> # min-backoff starts with 500 ms and with each attempted retry, back-off
> increments double, capped at 30 sec max
> # min-backoff starts with 500 ms and with each attempted retry, back-off
> increments by 1 sec, capped at 30 sec max
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
