Skip to content

Retry on 429, 499 also.#1768

Merged
dcherian merged 2 commits intomainfrom
r2-slowdown
Mar 5, 2026
Merged

Retry on 429, 499 also.#1768
dcherian merged 2 commits intomainfrom
r2-slowdown

Conversation

@dcherian
Copy link
Copy Markdown
Collaborator

@dcherian dcherian commented Mar 5, 2026

Closes #1767

Copy link
Copy Markdown
Collaborator

@paraseba paraseba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @dcherian !!!

@dcherian dcherian enabled auto-merge (squash) March 5, 2026 18:47
@dcherian dcherian changed the title Retry on 429 also. Retry on 429, 499 also. Mar 5, 2026
@dcherian dcherian merged commit 9a48a8b into main Mar 5, 2026
19 of 20 checks passed
@dcherian dcherian deleted the r2-slowdown branch March 5, 2026 18:59
ianhi added a commit that referenced this pull request Mar 6, 2026
Add HTTP 429 (Too Many Requests) and 499 (Client Closed Request) to
the custom S3 retry classifier. R2 sends 429 for slowdown (vs S3's 503),
and Tigris can respond with 499.

Cherry-picked from main: 9a48a8b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handle R2 slowdown errors

3 participants