Bug #17561

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

Added by Tom Clegg 8 months ago. Updated 6 months ago.

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

0%

Estimated time:
Story points:
-

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

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

Related to Arvados - Feature #17751: [arvados-dispatch-cloud] expose rate-limiting condition in metricsNew

History

#1 Updated by Tom Clegg 8 months ago

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

#2 Updated by Nico César 6 months ago

  • Assigned To set to Nico César

#3 Updated by Tom Clegg 6 months ago

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

#4 Updated by Tom Clegg 6 months ago

  • Description updated (diff)

#5 Updated by Nico César 6 months ago

  • Assigned To deleted (Nico César)

Also available in: Atom PDF