Issues with Leader Election in TiDB

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

Original topic: tidb的leader选举问题

| username: SianoWang

[TiDB Usage Environment] Development Environment
[TiDB Version] 6.5.2
[Reproduction Path] If one TiKV is manually downed, the leader will shift to the third node, but after restarting the downed TiKV, the leader reverts to being concentrated on only 2 nodes.
[Encountered Problem: Phenomenon and Impact] Out of three TiKV nodes, the leader is concentrated on only 2 nodes.
[Resource Configuration]

[Attachments: Screenshots/Logs/Monitoring]

Thanks to Kongdom’s link and h5n1’s guidance, my doubts have been resolved.
Finally, here’s a screenshot for future reference.

| username: 裤衩儿飞上天 | Original post link

  1. What is the leader score situation of the three TiKV nodes?
  2. Have weights been set?
  3. Have labels been set?
| username: Kongdom | Original post link

| username: h5n1 | Original post link

Check pd-ctl scheduler show to see if there is an evict scheduler.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.