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

cluster: fix tikv not upgraded on error increasing schedule limit #1401

Merged
merged 1 commit into from
Jun 4, 2021

Conversation

AstroProfundis
Copy link
Contributor

What problem does this PR solve?

The upgrade process of TiKV nodes may be skipped unexpectedly if increasing schedule limit failed

Check List

Tests

  • Manual test (add detailed scripts or steps below)

Related changes

  • Need to cherry-pick to the release branch

Release notes:

cluster: fix tikv not upgraded on error increasing schedule limit

@AstroProfundis AstroProfundis added type/bug-fix Categorizes PR as a bug-fix category/stability Categorizes issue or PR as a stability enhancement. labels Jun 3, 2021
@AstroProfundis AstroProfundis self-assigned this Jun 3, 2021
@ti-chi-bot ti-chi-bot requested a review from lucklove June 3, 2021 09:02
@ti-chi-bot ti-chi-bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 3, 2021
@AstroProfundis AstroProfundis added this to the v1.4.5 milestone Jun 3, 2021
@lucklove
Copy link
Member

lucklove commented Jun 3, 2021

/lgtm

@ti-chi-bot
Copy link
Member

@lucklove: Please use GitHub review feature instead of /lgtm [cancel] when you want to submit review to the pull request.
For how to use GitHub review feature, see also this document provided by GitHub.

For the reason we drop support to the commands, see also this page.
This reply is being used as a temporary reply during the migration of review process and will be removed on July 1st.

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.

@lucklove
Copy link
Member

lucklove commented Jun 3, 2021

/merge

@ti-chi-bot
Copy link
Member

@lucklove: /merge in this pull request requires 1 approval(s).

In response to this:

/merge

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

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • lucklove

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 the status/LGT1 Indicates that a PR has LGTM 1. label Jun 3, 2021
@AstroProfundis
Copy link
Contributor Author

/merge

@ti-chi-bot
Copy link
Member

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

Commit hash: bfacff3

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jun 3, 2021
@codecov-commenter
Copy link

Codecov Report

Merging #1401 (bfacff3) into master (b12ae28) will increase coverage by 27.22%.
The diff coverage is 20.00%.

Impacted file tree graph

@@             Coverage Diff             @@
##           master    #1401       +/-   ##
===========================================
+ Coverage   25.33%   52.56%   +27.22%     
===========================================
  Files         266      291       +25     
  Lines       20611    22494     +1883     
===========================================
+ Hits         5222    11824     +6602     
+ Misses      14586     8749     -5837     
- Partials      803     1921     +1118     
Flag Coverage Δ
cluster 39.19% <20.00%> (?)
dm 24.56% <0.00%> (?)
integrate 46.76% <20.00%> (+31.27%) ⬆️
playground 13.73% <ø> (?)
tiup 15.49% <ø> (ø)
unittest 21.66% <ø> (ø)

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

Impacted Files Coverage Δ
pkg/cluster/operation/upgrade.go 57.27% <20.00%> (ø)
components/playground/instance/tikv.go 67.34% <0.00%> (ø)
pkg/cluster/operation/telemetry.go 0.00% <0.00%> (ø)
pkg/cluster/operation/operation.go 78.26% <0.00%> (ø)
pkg/cluster/operation/destroy.go 54.23% <0.00%> (ø)
components/playground/instance/pump.go 0.00% <0.00%> (ø)
pkg/cluster/operation/systemd.go 70.00% <0.00%> (ø)
pkg/logger/debug.go 16.66% <0.00%> (ø)
components/playground/instance/pd.go 73.91% <0.00%> (ø)
components/playground/instance/instance.go 45.45% <0.00%> (ø)
... and 207 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b12ae28...bfacff3. Read the comment docs.

@ti-chi-bot ti-chi-bot merged commit 49248ac into pingcap:master Jun 4, 2021
@AstroProfundis AstroProfundis deleted the fix-upgrade branch June 4, 2021 08:05
@AstroProfundis AstroProfundis modified the milestones: v1.4.5, v1.5.0 Jun 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category/stability Categorizes issue or PR as a stability enhancement. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1. type/bug-fix Categorizes PR as a bug-fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants