Retry on "429 Too Many Requests" [Request]

[apaatsio]

It would be convenient to automatically re-add the request to the queue if server returns 429 Too Many Requests error. This should be configurable so we can set the maximum number of retries.

This is for situations where the network is not optimal (e.g. bad network can cause bursts and the rate limit to exceed at the server). Another situation is when you have two clients using the same API at the same time. If both clients are sending requests at the maximum rate, the total will be 2x rate limit and a lot of 429s.

[bhollis]

That'd be cool! Would you want to take a crack at submitting a PR for that?

On Tuesday, July 5, 2016, Antti Ahti [email protected] wrote:

It would be convenient to automatically re-add the request to the queue if
server returns 429 Too Many Requests error. This should be configurable so
we can set the maximum number of retries.

This is for situations where the network is not optimal (e.g. bad network
can cause bursts and the rate limit to exceed at the server). Another
situation is when you have two clients using the same API at the same time.
If both clients are sending requests at the maximum rate, the total will be
2x rate limit and a lot of 429s.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1, or mute the
thread
https://github.com/notifications/unsubscribe/AATHeFzwS4z8MnROOLN1E-yGRhqFPVaWks5qShZfgaJpZM4JE4wj
.

[apaatsio]

I might have time next week for that. Let's see :)