Catch KMSThrottlingException errors - backoff and wait in that case
Open
- Dominant language
- JavaScript
- Stars
- 18
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
We could add this error to the list of known, retryable exceptions here:
https://github.com/mapbox/kine/blob/7f505615fe3b3e9137d9188ae5bf262d4bcb7da9/lib/kcl.js#L177
They do not happen often, but when they do it's better to have the delay and retry be managed by Kine.
cc/ @mick @l-r
Contributor guide
Research direction
Start in lib/kcl.js at the linked list of known retryable exceptions and inspect how retry delays are applied. Add KMSThrottlingException to that handling, then verify that this error follows the existing delay-and-retry path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- backend, data-engineering
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100