Skip to content
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

better to add the route53 request limits in _retry.json #91

Closed
henrysher opened this issue Jul 26, 2013 · 3 comments
Closed

better to add the route53 request limits in _retry.json #91

henrysher opened this issue Jul 26, 2013 · 3 comments
Assignees

Comments

@henrysher
Copy link
Contributor

better to add route53 request limits here:
https://github.com/boto/botocore/blob/develop/botocore/data/aws/_retry.json

Details can be found in the issue #1618 in boto:
boto/boto#1618

toastdriven pushed a commit to toastdriven/botocore that referenced this issue Aug 9, 2013
…ers now support epoch times, both as input formats as well as output formats. Fixes boto#91.
@ghost ghost assigned toastdriven and jamesls Aug 19, 2013
@mtdowling
Copy link
Contributor

Is this still an issue in botocore? Can you send a PR if it is?

@rayluo
Copy link
Contributor

rayluo commented Sep 30, 2015

The "accepted" and "closing soon if no response" labels just don't mix. Closing for now. Feel free to reopen if needed.

@rayluo rayluo closed this as completed Sep 30, 2015
@rayluo rayluo reopened this Sep 30, 2015
@jamesls
Copy link
Member

jamesls commented Sep 30, 2015

Sorry, just to clarify the remaining work here:

From the route53 docs (http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DNSLimitations.html):

All requests – Five requests per second per AWS account. If you submit more than five requests per second, Amazon Route 53 returns an HTTP 400 error (Bad request). The response header also includes a Code element with a value of Throttling and a Message element with a value of Rate exceeded.

Therefore the pending work remaining is to add the status 400 Code=Throttling rule to our _retry.json. Once this is done we can close this issue out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants