scheduler: unexpected increase in hot scheduler v2
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 783
- Avg merge
- 5d 21h
- Merged PRs (30d)
- 36
Description
## Bug Report
### What did you do?
tpcc bench
### What did you expect to see?
### What did you see instead?
store-6 become higher is not in line with expectations, now the strategy is very conservative, no matter what will not go to destroy the first dimension.
And there is no other write schedule when store-6 becomes higher.
### What version of PD are you using (`pd-server -V`)?
2eb76c889c7cd0d23f0c63d663944389165870cb
scheduler config balance-hot-region-scheduler set write-leader-priorities "query","byte"
scheduler config balance-hot-region-scheduler set strict-picking-store false
scheduler config balance-hot-region-scheduler set rank-formula-version v2
Contributor guide
Assessment
This issue has not been assessed yet.