have https protocol driver automatically back off when it gets the Too Many Requests error? #935
Labels
coverage
unit or flow tests do not notice changes here
Design
Problem hard to fix, affects design.
Developer
not a problem, more of a note to self for devs about work to do.
Discussion_Needed
developers should discuss this issue.
enhancement
New feature or request
Priority 4 - Strategic
would benefit multiple use cases if resolved
ReliabilityRecovery
improve behaviour in failure situations.
so... sr3 processes messages in batches, and amortizes connections over those batches. If one message transfer fails, it just tries the next one. For many cases (like 404) that's fine, maybe the next one does exist, but in the Too Many Requests case, it will never help, and likely hurt:
It would be good to put some smarts in the https downloader to back off for a bit when this error is received.
The text was updated successfully, but these errors were encountered: