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
AWS General Reference for API Retries claims SDKs implement automatic retry logic and instructs non-SDK users to retry requests that receive throttling errors. SDK for Go API Reference recommends an exponential backoff retry algorithm for the “PriorRequestNotComplete” error code.
SDK should use configured retry options upon receiving “PriorRequestNotComplete” error code.
PriorRequestNotComplete
If Amazon Route 53 can't process a request before the next request arrives,
it will reject subsequent requests for the same hosted zone and return an
HTTP 400 error (Bad request). If Amazon Route 53 returns this error repeatedly
for the same request, we recommend that you wait, in intervals of increasing
duration, before you try the request again. http://docs.aws.amazon.com/sdk-for-go/api/service/route53/#example_Route53_ChangeResourceRecordSets
Thanks for taking the time to find and add the throttle error code to the SDK @kcolemangt. Let us know if you find anything else, or have additional feedback.
AWS General Reference for API Retries claims SDKs implement automatic retry logic and instructs non-SDK users to retry requests that receive throttling errors. SDK for Go API Reference recommends an exponential backoff retry algorithm for the “PriorRequestNotComplete” error code.
SDK should use configured retry options upon receiving “PriorRequestNotComplete” error code.
This has already been implemented in another AWS SDK:
aws/aws-sdk-js#1166
https://github.com/aws/aws-sdk-js/blob/b0de518dab2ceb08a62ad2abe59a222b62d90003/lib/services/route53.js
I will submit a PR.
The text was updated successfully, but these errors were encountered: