Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement unavailable service error retry strategy #15601

Closed
dkocher opened this issue Feb 1, 2024 · 0 comments · Fixed by #15672
Closed

Implement unavailable service error retry strategy #15601

dkocher opened this issue Feb 1, 2024 · 0 comments · Fixed by #15672
Labels
b2 Backblaze B2 Protocol Implementation enhancement
Milestone
8.8.0

Comments

@dkocher
Copy link
Contributor

dkocher commented Feb 1, 2024

When service is unavailable with an error such as No tomes available we may want to have a retry strategy for requests enabled that is independent of the generic setting in Connection → Timeouts.

The service is temporarily unavailable. The human-readable message identifies the nature of the issue, in general we recommend retrying with an exponential backoff between retries in response to this error. 1

Footnotes

  1. https://www.backblaze.com/docs/cloud-storage-native-api-error-handling-and-status-codes ↩
@dkocher dkocher added b2 Backblaze B2 Protocol Implementation enhancement labels Feb 1, 2024
@dkocher dkocher added this to the 8.8.0 milestone Feb 29, 2024
This was referenced Feb 29, 2024
Merged
Closed
dkocher added a commit that referenced this issue Mar 6, 2024
@dkocher
Merge pull request #15672 from iterate-ch/feature/GH-15601
4f09e9f 
Back off either for a raw network socket or connection timeout or if …
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
b2 Backblaze B2 Protocol Implementation enhancement
Projects
None yet
Milestone
8.8.0
Development

Successfully merging a pull request may close this issue.

Back off either for a raw network socket or connection timeout or if … iterate-ch/cyberduck
1 participant
@dkocher