resource control: use RUv2 consumption for RUv2 keyspaces
Open
contribution
needs-type
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 783
- Avg merge
- 5d 21h
- Merged PRs (30d)
- 36
Description
## Development Task
Resource control already tracks the RU version policy per keyspace and TiDB reports statement-level RUv2 consumption back to the PD client. However, the client-side token bucket still uses v1 RU (`RRU + WRU`) for token deduction and request judgement.
When a keyspace is configured to use RUv2, resource control should use RUv2 consumption for token accounting so throttling follows the active RU model.
Contributor guide
Assessment
This issue has not been assessed yet.