-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should retry Route53 requests that get PriorRequestNotComplete errors #1166
Comments
I think the easy way to do this would be to modify the Route53 service to override |
Hi @Answashe |
Hi @Answashe |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DNSLimitations.html#limits-api-requests has a description of the PriorRequestNotComplete error. In most cases this can be retried with the normal exponential backoff strategy. In fact, that's what boto does.
boto works a little differently in that its retry behavior is defined as data instead of code, but see boto/botocore#682 for the corresponding change in boto.
The text was updated successfully, but these errors were encountered: