mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[PR #2443] [MERGED] retry request on HTTP 429 error #2540
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#2540
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/2443
Author: @blinkseb
Created: 4/12/2024
Status: ✅ Merged
Merged: 4/14/2024
Merged by: @gaul
Base:
master← Head:feat-retry-on-429📝 Commits (1)
8bb0813retry request on HTTP 429 error📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
src/curl.cpp(+1 -0)📄 Description
Hi,
Some non-Amazon S3 implementation have a stricter quota / rate-limiting than AWS (for example Scaleway). It means that it's quiet easy to be rate limited in case of large buckets for example. In this case, an HTTP error 429 is returned and the request fails.
This PR makes s3fs retry when an HTTP error 429 is returned, as it's already doing for 500 and 503 errors.
Thanks!
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.