-
Notifications
You must be signed in to change notification settings - Fork 500
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
Do not error in pvc_modifier, when a manual TiKV eviction is requested. #5302
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #5302 +/- ##
==========================================
- Coverage 57.48% 57.44% -0.05%
==========================================
Files 252 252
Lines 30594 30593 -1
==========================================
- Hits 17586 17573 -13
- Misses 11271 11278 +7
- Partials 1737 1742 +5
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: csuzhangxc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
New changes are detected. LGTM label has been removed. |
/cherry-pick release-1.5 |
@csuzhangxc: new pull request created to branch In response to this:
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. |
What problem does this PR solve?
pvc_modifier keeps throwing errors even if a manual TiKV region leader eviction is requested by annotating the pod per the documentation here:
https://docs.pingcap.com/tidb-in-kubernetes/stable/maintain-a-kubernetes-node#evict-tikv-region-leader
This happens even if no volume modification is actually requested.
What is changed and how does it work?
Do not keep checking if eviction has ended during pvc_modifier sync.
If an annotation does exist for resize, delete it and throw an error once alone to give pod_control.go a chance to stop the eviction. But do not block forever until it is removed as this may have been requested by user manually and should not throw errors.
Code changes
Tests
Side effects
Related changes
Release Notes
Please refer to Release Notes Language Style Guide before writing the release note.