Long exponential backoff on `SlowDown` errors
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
It would be a nice thing to do for your bucket's well-being.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is identified; start by locating the S3 request-handling entry point and its retry/backoff logic. Confirm the intended behavior for SlowDown errors and add coverage showing the long exponential backoff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100