Actions
Feature #19984
closedGo arvados.Client responds to 503 errors by limiting outgoing connection concurrency
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.
Updated by Tom Clegg about 2 years ago
- Related to Bug #19973: Dispatcher responds to 503 errors by limiting container concurrency added
Updated by Tom Clegg about 2 years ago
- Story points set to 2.0
- Target version set to Future
Updated by Peter Amstutz about 2 years ago
- Target version changed from Future to To be scheduled
Updated by Peter Amstutz about 2 years ago
- Target version changed from To be scheduled to 2023-02-15 sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2023-02-15 sprint to 2023-03-01 sprint
Updated by Tom Clegg about 2 years ago
- Related to Feature #19972: Go arvados.Client retry with backoff added
Updated by Tom Clegg about 2 years ago
- Assigned To set to Tom Clegg
- Status changed from New to In Progress
Updated by Tom Clegg about 2 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|7c013f919b5db9336833dbe855349600449a993d.
Actions