[FEATURE REQ] Align with azcopy retry settings (20 attempts)

Library or service name. All of Azure.Storage

Is your feature request related to a problem? Please describe. I have ran into timeouts that look like this, trying to upload ~400MB files using slow connections:

System.AggregateException: Retry failed after 6 tries. (Error while copying content to a stream.) (Error while copying content to a stream.) (Error while copying content to a stream.) (Error while copying content to a stream.) (Error while copying content to a stream.) (Error while copying content to a stream.)
 ---> Azure.RequestFailedException: Error while copying content to a stream.
 ---> System.Net.Http.HttpRequestException: Error while copying content to a stream.
 ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
 ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.

I suspect azcopy has more optimized retry parameters, especially for upload. Looking at their code, the main difference seems to be the retry count of 20 (for uploads): https://github.com/Azure/azure-storage-azcopy/blob/2c30af330b681d3a1f31db32e11245eafce9c5c3/ste/xfer.go#L36

Compare this to the Azure SDK retry count of 5 (which translates to a total of 6 attempts): https://github.com/Azure/azure-sdk-for-net/blob/00d31be869a010d4b5801726d11bf83f39031248/sdk/storage/Azure.Storage.Common/src/Shared/Constants.cs#L15

[jsquire]

Thank you for your feedback. Tagging and routing to the team best able to assist.

[msftbot[bot]]

Hi @ohadschn, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.