Actions
Bug #3419
closed[SDKs] Perl client library should retry failed API requests after errors like Gateway Timeout
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
SDKs
Target version:
-
Story points:
1.0
Description
Most importantly, crunch-job must try hard to avoid throwing away a long-running job due to a transient failure.
Updated by Tom Clegg over 10 years ago
- Subject changed from [SDK] Ruby and CLI libraries should retry failed API requests after errors like Gateway Timeout to [SDK] Client libraries should retry failed API requests after errors like Gateway Timeout
- Description updated (diff)
Updated by Tom Clegg over 10 years ago
- Subject changed from [SDK] Client libraries should retry failed API requests after errors like Gateway Timeout to [SDKs] Client libraries should retry failed API requests after errors like Gateway Timeout
- Category set to SDKs
Updated by Radhika Chippada over 10 years ago
I think it is desirable that we create a separate bug for each of the client libraries. This helps with reviewing, testing. That way we can also divvy up the work more effectively.
Updated by Peter Amstutz over 10 years ago
- Target version set to Arvados Future Sprints
Updated by Tom Clegg over 10 years ago
- Target version changed from Arvados Future Sprints to 2014-10-08 sprint
Updated by Tom Clegg over 10 years ago
- Subject changed from [SDKs] Client libraries should retry failed API requests after errors like Gateway Timeout to [SDKs] Perl client library should retry failed API requests after errors like Gateway Timeout
- Description updated (diff)
Updated by Brett Smith about 10 years ago
I think the general approach is:
- Add a
num_retries
argument to Arvados::Request::process_request. It handles the actual retry loop (a la Python), backing off between requests that should be retried. - Add
num_retries
arguments to Arvados::ResourceMethod::execute and the save, update_attributes, and reload methods of Arvados::ResourceProxy. These should simply be propagated down to the appropriate lower calls, so they reach Arvados::Request. This should be a "keyword argument" in the methods that already take those.
It's not expressly specified but I figure this story wants to see crunch-job use this support.
Updated by Ward Vandewege about 10 years ago
- Target version changed from 2014-10-08 sprint to Arvados Future Sprints
Updated by Tom Morris about 8 years ago
- Assigned To changed from Brett Smith to Tom Morris
Updated by Tom Morris about 8 years ago
- Status changed from New to Closed
- Assigned To deleted (
Tom Morris) - Target version deleted (
Arvados Future Sprints)
Done at some point in the past
Actions