[PR #2443] [MERGED] retry request on HTTP 429 error #2540

Closed
opened 2026-03-04 02:06:04 +03:00 by kerem · 0 comments
Owner

📋 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: masterHead: feat-retry-on-429


📝 Commits (1)

  • 8bb0813 retry 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.

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/2443 **Author:** [@blinkseb](https://github.com/blinkseb) **Created:** 4/12/2024 **Status:** ✅ Merged **Merged:** 4/14/2024 **Merged by:** [@gaul](https://github.com/gaul) **Base:** `master` ← **Head:** `feat-retry-on-429` --- ### 📝 Commits (1) - [`8bb0813`](https://github.com/s3fs-fuse/s3fs-fuse/commit/8bb0813bcc0f89d29e87d435ae7813e09258ff1d) retry request on HTTP 429 error ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/curl.cpp` (+1 -0) </details> ### 📄 Description <!-- -------------------------------------------------------------------------- Please describe the purpose of the pull request(such as resolving the issue) and what the fix/update is. --------------------------------------------------------------------------- --> 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! --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-04 02:06:04 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#2540
No description provided.