UCP: Add a new diagnostic rules for diagnosing hotspots

lonng commented 4 years ago

Description

This is a sub-task of #14983.

Some workloads may experience read and write hotspots. We need a new diagnostic rule to locate the region which is hotspots and give the user a suggestion in the details column to help user resolve it.

Suggestions might be:

split region if the region is read hotspots. (see: https://pingcap.com/docs/stable/reference/sql/statements/split-region/)
check is there an auto_increment primary key in some tables, which may cause write hotspots. (SHARD_ROW_ID_BITS)

Score

160

Mentor(s)

@crazycs520

Contact the mentors: #tidb-challenge-program channel in TiDB Community Slack Workspace

Recommended Skills

Go
SQL

Learning Materials

Chinese: TiDB 精选技术讲解文章
English: Awesome-Database-Learning

AndrewDi commented 4 years ago

/pick-up-challenge

sre-bot commented 4 years ago

"easy" issue is not available since you have got 200 score in this repo. Please pickup "medium" or "hard" directly. Or you can pick up "easy" Issue in other repos. Thank you.

ziyi-yan commented 4 years ago

/pick-up-challenge

sre-bot commented 4 years ago

@ziyi-yan pick up issue success

ziyi-yan commented 4 years ago

/give-up-challenge

sre-bot commented 4 years ago

@ziyi-yan give up issue success

AngleNet commented 4 years ago

/pick-up-chanllenge

TennyZhuang commented 4 years ago

/pick-up-challenge

sre-bot commented 4 years ago

"easy" issue is not available since you have got 200 score in this repo. Please pickup "medium" or "hard" directly. Or you can pick up "easy" Issue in other repos. Thank you.

pingcap / tidb