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

Reduct jitter feature #1033

Closed
2 tasks
King-Dylan opened this issue Dec 31, 2020 · 2 comments
Closed
2 tasks

Reduct jitter feature #1033

King-Dylan opened this issue Dec 31, 2020 · 2 comments
Labels
priority/P1 Indicates that the priority of a issue is high. type/feature-request Categorizes issue as related to a new feature.
Milestone

Comments

@King-Dylan
Copy link
Contributor

King-Dylan commented Dec 31, 2020

Feature Request

Reduct jitter feature
Is your feature request related to a problem? Please describe:

  • before upgrade check pd miss-peer pending-peer and give a suggestion :solve miss-peer or ignore . Check the status of the region before the upgrade to reduce upgrade jitter or failure caused by the abnormal region before the upgrade.
  • before eviting tikv leader configure leader-scheduler-limit store-limit region-scheduler-limit.speed up leader transfer, after upgrade change to default value。can take the original value and add a number, and make a judgment of not greater than leader-scheduler-limit(64) store-limit(1024) region-scheduler-limit(1024) example:
    1.tiup cluster upgrade xxxx
    2.background(get default value)
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 config show |grep leader-schedule-limit
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 config show |grep region-schedule-limit
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 store limit
    3.background
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 config set leader-schedule-limit {default value}+32
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 config set region-schedule-limit {default value}+512
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 store limit all {default value}+512
    4.tikv rolling upgrade end
    5.background(get value and check default >=0)
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 config show |grep leader-schedule-limit
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 config show |grep region-schedule-limit
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 store limit
    6.background (setback default value)
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 config set leader-schedule-limit {value}-32
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 config set region-schedule-limit {value}-512
    tiup ctl pd -u xxx.xxx.xxx.xxx:2379 store limit all {value}-512

Describe the feature you'd like:

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

@King-Dylan King-Dylan added the type/feature-request Categorizes issue as related to a new feature. label Dec 31, 2020
@King-Dylan
Copy link
Contributor Author

King-Dylan commented Dec 31, 2020

pd reduce jitter:
when rolling restart PD, confirm that each peers can server : #1032
Upgrade pd that is not leader first then upgrade pd leader in tiup upgrade: #664

@King-Dylan King-Dylan added this to the v1.4.0 milestone Dec 31, 2020
@King-Dylan King-Dylan added the priority/P1 Indicates that the priority of a issue is high. label Dec 31, 2020
@AstroProfundis
Copy link
Contributor

I'm closing this as both linked issues are closed, please reopen if there's anything more need to be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/P1 Indicates that the priority of a issue is high. type/feature-request Categorizes issue as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants