Rename Aggressive Locking to Fair Locking
Open
type/enhancement
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Enhancement
After discussion, we decided to rename the feature *[Aggressive Locking](https://github.com/tikv/tikv/issues/13298)* into *Fair Locking*. The former name doesn't make sense for users that don't know much about the internal mechanics of TiDB, but the new name tells users the most intuitive deference of the new lock model.
Contributor guide
Research direction
The issue provides no file or test names; begin by searching the TiDB repository for “Aggressive Locking” and review the linked TiKV discussion for scope. Done means the feature is consistently presented as “Fair Locking” wherever the old user-facing name appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100