Check the plan based RU behavior when the txn need retry
Open
type/enhancement
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Enhancement
Check what the RU calculation is when the txn retries its execution.
It's possible that we may only record the first execution or the last execution.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the RU calculation and the transaction retry handling, then trace whether retries record the first execution, the last execution, or another result. Done means the retry behavior is established and covered by an appropriate test or documented decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100