Project

General

Profile

Actions

Feature #19984

open

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

Added by Tom Clegg 3 days ago. Updated 3 days ago.

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

Related to Arvados - Bug #19973: Dispatcher responds to 503 errors by limiting container concurrencyNew

Actions
Actions #1

Updated by Tom Clegg 3 days ago

  • Related to Bug #19973: Dispatcher responds to 503 errors by limiting container concurrency added
Actions #2

Updated by Tom Clegg 3 days ago

  • Story points set to 2.0
  • Target version set to To be groomed
Actions #3

Updated by Peter Amstutz 3 days ago

  • Target version changed from To be groomed to To be scheduled
Actions

Also available in: Atom PDF