Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propose: let PD consider different disk for balance #1052

Open
siddontang opened this issue May 7, 2018 · 0 comments
Open

Propose: let PD consider different disk for balance #1052

siddontang opened this issue May 7, 2018 · 0 comments
Labels
component/schedule Scheduling logic. status/discussion-wanted The issue needs to be discussed.

Comments

@siddontang
Copy link
Contributor

although we advise users to deploy all TiKV on SSD, sometimes, the users still use HDD or even different disks.

If the users deploy TiKVs on different disks, this may cause a problem (Wooden Barrel Theory), because PD will balance the traffic fairly, and the TiKVs on the HDD will suffer the same load with other TiKVs on the SSD and provide a high latency service, which can cause the total performance reduction.

Although we can use label or set weight, etc. manually to avoid this, it is still better to let PD know the system information for better balance. The TiKV can report its disk type (HDD or SSD) to the PD, and PD will prefer balancing Hot Leaders on the SSD over HDD.

/cc @disksing @nolouch

@siddontang siddontang added the status/discussion-wanted The issue needs to be discussed. label May 7, 2018
@rleungx rleungx added the component/schedule Scheduling logic. label May 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/schedule Scheduling logic. status/discussion-wanted The issue needs to be discussed.
Projects
None yet
Development

No branches or pull requests

2 participants