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.

Sign up for GitHub

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

Jump to bottom

Use CI to continuously monitor the scheduling efficiency in typical scenarios. #543

Open
disksing opened this issue Feb 27, 2017 · 1 comment
Open

Use CI to continuously monitor the scheduling efficiency in typical scenarios. #543

disksing opened this issue Feb 27, 2017 · 1 comment
Labels
component/schedule Scheduling logic.

Comments

@disksing
Copy link
Contributor

Now we only have some tests for scheduling correctness, but no test case or CI for its efficiency. We should consider constructing some tests with reference to the following scenarios:

  1. add/remove a tikv-server node.
  2. restart all tikv-servers (at almost the same time).
  3. rolling restart all tikv-servers.
  4. tikv-server reports busy.
  5. hot regions split fast.
  6. increase/decrease replica count.
    ...
@disksing disksing added status/discussion-wanted The issue needs to be discussed. status/TODO The issue will be done in the future. labels Feb 27, 2017
@rleungx rleungx added component/schedule Scheduling logic. and removed status/discussion-wanted The issue needs to be discussed. status/TODO The issue will be done in the future. labels May 11, 2020
@rleungx
Copy link
Member

rleungx commented May 11, 2020

The issue can be replaced by implementing the bench bot for scheduling in our CI environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/schedule Scheduling logic.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@disksing @rleungx