Project

General

Profile

Actions
Copy link

Bug #17561

open

[arvados-dispatch-cloud] inst.SetTags() and inst.Destroy() should respect rate-limiting responses from cloud provider

Added by Tom Clegg over 3 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-
Release:
Postponed
Release relationship:
Auto

Description

Currently, a-d-c and its drivers detect when the cloud provider returns a "too many requests" response to a "list instances" or "create instance" API call, and waits for some time to elapse before trying the same type of call.

We should also detect & handle those responses for "update instance tags" and "destroy instance" calls.

Related issues 2 (1 open — 1 closed)

Related to Arvados - Bug #17529: [a-d-c] AWS/EC2 driver should return a RateLimitError to dispatcher if the upstream error is RequestLimitExceededResolvedTom Clegg04/14/2021

Actions
Related to Arvados - Feature #17751: [arvados-dispatch-cloud] expose rate-limiting condition in metricsNewNico César

Actions
Actions
Copy link
 #1

Updated by Tom Clegg over 3 years ago

  • Related to Bug #17529: [a-d-c] AWS/EC2 driver should return a RateLimitError to dispatcher if the upstream error is RequestLimitExceeded added
Actions
Copy link
 #2

Updated by Nico César over 3 years ago

  • Assigned To set to Nico César
Actions
Copy link
 #3

Updated by Tom Clegg over 3 years ago

  • Related to Feature #17751: [arvados-dispatch-cloud] expose rate-limiting condition in metrics added
Actions
Copy link
 #4

Updated by Tom Clegg over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by Nico César over 3 years ago

  • Assigned To deleted (Nico César)
Actions
Copy link
 #6

Updated by Lucas Di Pentima almost 2 years ago

  • Release set to 60
Actions
Copy link

Also available in: Atom PDF