Actions
Feature #19984
open
Go arvados.Client responds to 503 errors by limiting outgoing connection concurrency
Start date:
Due date:
% Done:
0%
Estimated time:
Story points:
2.0
Description
Before starting an outgoing request, arvados.Client should wait until the number of concurrent outgoing connections would not exceed
- 0, if a 503 response was received <1s ago
- the outgoing connection concurrency limit specified by the caller, if any
- an automatic outgoing concurrency limit which gets decreased by 50% on each 503 and increased by max(10%,1) on each 2xx
The caller should be able to retrieve the client's current connection limit. This will enable dispatchcloud, for example, to reduce the number of containers it attempts to run concurrently in #19973.
Related issues
Updated by Tom Clegg 3 days ago
- Related to Bug #19973: Dispatcher responds to 503 errors by limiting container concurrency added
Updated by Peter Amstutz 3 days ago
- Target version changed from To be groomed to To be scheduled
Actions