Fine-grained backoff
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 425
- Forks
- 163
- Avg merge
- 10h 51m
- Merged PRs (30d)
- 3
Description
Currently we have DEFAULT_REGION_BACKOFF, OPTIMISTIC_BACKOFF, and PESSIMISTIC_BACKOFF. The same Backoff is used almost everywhere in a certain transaction.
- There can be more fine-grained
Backoffs for better performance and user experience. - Record the backoff history
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the existing DEFAULT_REGION_BACKOFF, OPTIMISTIC_BACKOFF, and PESSIMISTIC_BACKOFF definitions and where Backoff is reused in transactions. Clarify the desired backoff granularity and history format before changing code; done means the design is agreed, fine-grained backoffs improve the relevant behavior, and backoff history is recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100