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

operator: When replacing-down-peer, it should not stop at the step of leave-joint-state #5789

Merged
merged 3 commits into from
Dec 19, 2022

Conversation

HunDunDM
Copy link
Member

Signed-off-by: HunDunDM hundundm@gmail.com

What problem does this PR solve?

Issue Number: Close #5788

What is changed and how does it work?

Rolled back some code from #5568 and added unittest.

Check List

Tests

  • Unit test

Code changes

Side effects

Related changes

  • Need to cherry-pick to the release branch

Release note

Fixed an issue that `replace-down-peer` could be too slow.

… leave-joint-state

Signed-off-by: HunDunDM <hundundm@gmail.com>
@ti-chi-bot
Copy link
Member

ti-chi-bot commented Dec 16, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • nolouch
  • rleungx

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. labels Dec 16, 2022
@HunDunDM
Copy link
Member Author

cc @ethercflow

@codecov
Copy link

codecov bot commented Dec 16, 2022

Codecov Report

Base: 75.72% // Head: 75.52% // Decreases project coverage by -0.20% ⚠️

Coverage data is based on head (8bb7c99) compared to base (544c86a).
Patch coverage: 100.00% of modified lines in pull request are covered.

❗ Current head 8bb7c99 differs from pull request most recent head 3066c18. Consider uploading reports for the commit 3066c18 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5789      +/-   ##
==========================================
- Coverage   75.72%   75.52%   -0.21%     
==========================================
  Files         330      330              
  Lines       32996    32996              
==========================================
- Hits        24987    24921      -66     
- Misses       5870     5916      +46     
- Partials     2139     2159      +20     
Flag Coverage Δ
unittests 75.52% <100.00%> (-0.21%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
server/schedule/operator/step.go 73.80% <100.00%> (+0.71%) ⬆️
pkg/errs/errs.go 75.00% <0.00%> (-25.00%) ⬇️
pkg/utils/tempurl/tempurl.go 45.00% <0.00%> (-15.00%) ⬇️
pkg/dashboard/adapter/manager.go 79.31% <0.00%> (-9.20%) ⬇️
...erver/config/service_middleware_persist_options.go 91.66% <0.00%> (-8.34%) ⬇️
server/tso/local_allocator.go 64.86% <0.00%> (-6.76%) ⬇️
server/region_syncer/client.go 79.85% <0.00%> (-6.72%) ⬇️
pkg/storage/kv/etcd_kv.go 79.71% <0.00%> (-5.80%) ⬇️
server/storage/storage.go 67.30% <0.00%> (-3.85%) ⬇️
server/schedulers/random_merge.go 62.50% <0.00%> (-3.13%) ⬇️
... and 22 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

Signed-off-by: HunDunDM <hundundm@gmail.com>
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Dec 19, 2022
@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Dec 19, 2022
@nolouch
Copy link
Contributor

nolouch commented Dec 19, 2022

/merge

@ti-chi-bot
Copy link
Member

@nolouch: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 8bb7c99

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Dec 19, 2022
@ti-chi-bot
Copy link
Member

@HunDunDM: Your PR was out of date, I have automatically updated it for you.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch release-6.5: #5795.

@nolouch nolouch deleted the fix-5788 branch December 19, 2022 07:57
ti-chi-bot added a commit that referenced this pull request Feb 6, 2023
… leave-joint-state (#5789) (#5795)

ref #5568, close #5788, ref #5789

Signed-off-by: HunDunDM <hundundm@gmail.com>

Co-authored-by: HunDunDM <hundundm@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. release-note Denotes a PR that will be considered when it comes time to generate release notes. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The Operator may stop at the step of leave-joint-state
4 participants