Skip to content
This repository has been archived by the owner on Aug 21, 2023. It is now read-only.

Automatically retry requests that fail with 429 Too Many Requests #130

Closed
rmartz opened this issue Jan 30, 2017 · 1 comment
Closed

Automatically retry requests that fail with 429 Too Many Requests #130

rmartz opened this issue Jan 30, 2017 · 1 comment

Comments

@rmartz
Copy link
Contributor

rmartz commented Jan 30, 2017

In azavea/climate-change-api#191 we instituted a rate limiter to prevent a single user from consuming too many system resources and denying other users access. Each user has a limit of 10 requests per minute, up to 5000 per day, and any requests after that limit has been reached fail with a HTTP 429 error. However, after the minute quota has cleared the blocked requests are perfectly OK to retry.

If a user has a report with more than 10 items or changes cities too frequently they are going to experience this problem, so we should ensure that the lab automatically retries requests that temporarily fail because of the user's quota.

@rmartz
Copy link
Contributor Author

rmartz commented Dec 12, 2017

Close in favor of #327

@maurizi maurizi closed this as completed Feb 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants