You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that the the error read: connection reset was deliberately made as a not retryable for internal retry mechanism. Could you, please, explain why this error is not retryable? Is it safe to implement our own custom retry mechanism just for this particular error?
Our motivation to retry this kind of errors is related to this issue.
Steps to reproduce
Nothing to reproduce
The text was updated successfully, but these errors were encountered:
Hi @AVoskoboinikov, thanks for reaching out and I do apologize for the long delay in response on this. You are correct in that connection reset errors are deliberately not retryable in the default retryer's logic. As @skmcgrail mentions in #2926 this behavior was introduced as part of commit c3d2710 because the SDK cannot determine the state of the API call on which the connection was reset, and we do not want to have the SDK blindly re-issue non-idempotent requests that were received and processed by the service before the connection was reset.
If you are confident that the requests you are issuing with the SDK are idempotent (or don't mind if non-idempotent requests upon which the connection is reset are duplicated from the service end) you can implement a custom retryer that does retry these errors.
Version of AWS SDK for Go?
v1.23.21
Version of Go (
go version
)?go1.12.9 darwin/amd64
What issue did you see?
This ticket is more a question to AWS folks rather than a bug/issue.
Check this file:
aws-sdk-go/aws/request/connection_reset_error.go
Current content is
I understand that the the error
read: connection reset
was deliberately made as a not retryable for internal retry mechanism. Could you, please, explain why this error is not retryable? Is it safe to implement our own custom retry mechanism just for this particular error?Our motivation to retry this kind of errors is related to this issue.
Steps to reproduce
Nothing to reproduce
The text was updated successfully, but these errors were encountered: