couchbaselabs / couchbaselabs/sdk-rfcs
0012_Adapt memcached error code handling for future proofing
- Dominant language
- No language data
- Stars
- 42
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
I believe the current behavior for all issues other than TMPFAIL is to pass them back to the application layer.
In some scenarios where the bucket isn't available yet and things like MB-13156, MB-12088/MB-14442 it's been suggested that clients should retry on all unknown errors.
Possible ideas are to come up with ranges for errors to know in advance what to retry and what to bubble up to the developer or just develop defaults.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the current handling of TMPFAIL and other errors before they reach the application layer. The issue references MB-13156, MB-12088, and MB-14442, but names no files or tests and does not settle whether retry ranges or default behavior should be used. A concrete done condition is not specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- memcached
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100