TidbCluster: disable evict leader for TiKV EBS modification (#5826) #5829
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated cherry-pick of #5826
What problem does this PR solve?
evict leader for TiKV may take a long time, and the performance drop without leader-eviction is very low.
So we decide to disable this leader-eviction behavior for TiKV EBS modification.
NOTE: do not upgrade TiDB Operator when some leader-eviction (with EBS modification, but do not include EBS size modification, ref #5101) is happening as after this PR no "remove evict-leader-scheduler" will be performed then some evict-leader-scheduler may be kept.
What is changed and how does it work?
Code changes
Tests
Side effects
Related changes
Release Notes
Please refer to Release Notes Language Style Guide before writing the release note.