Unable to Evict TiKV Region Leader

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 无法驱逐tikv Region Leader

| username: Leez

【TiDB Usage Environment】Production
【TiDB Version】5.4.0
【Encountered Problem】Unable to evict TiKV Region Leader
【Reproduction Path】Executed ALTER TABLE t SHARD_ROW_ID_BITS = 4;
【Problem Phenomenon and Impact】
【TiDB Operator Version】: tidb-operator-v1.2.7
【K8s Version】: 1.20.15
After executing the eviction command, more than an hour has passed, and the Region Leader has not been evicted; instead, the number has increased.

kubectl -n prod annotate pod tikv-15 tidb.pingcap.com/evict-leader="none"
2
| username: DBAhank | Original post link
  1. First, check if the corresponding cluster components are all running.
  2. We habitually use pd-ctl to connect to the tipd node and execute schedular add evict-leader-schedular number to evict the leader. You can try this.
3
| username: Leez | Original post link

Thanks, I’ll give it a try.

4
| username: Leez | Original post link

It’s already working. I didn’t notice the operator version. The methods for evicting Region Leaders are different between 1.2 and 1.3. :tired_face:

5
| username: system | Original post link

This topic will be automatically closed 60 days after the last reply. No new replies are allowed.