Project

General

Profile

Actions

Feature #19984

closed

Go arvados.Client responds to 503 errors by limiting outgoing connection concurrency

Added by Tom Clegg about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
SDKs
Target version:
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.


Subtasks 1 (0 open1 closed)

Task #20116: Review 19973-dispatch-throttleResolvedTom Clegg02/21/2023Actions

Related issues

Related to Arvados - Bug #19973: Dispatcher responds to 503 errors by limiting container concurrencyResolvedTom Clegg02/16/2023Actions
Related to Arvados - Feature #19972: Go arvados.Client retry with backoffResolvedTom Clegg03/08/2023Actions
Actions

Also available in: Atom PDF