After TIUP RELOAD, the leader of a certain node became 0

Translated
1

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

Original topic: TIUP RELOAD后 某个节点的leader变为0了

| username: TiDBer_bOR8eMEn

[TiDB Usage Environment] Production Environment
[TiDB Version] 5.2.3

Why did the number of leaders on one machine become 0 after I reloaded, even though the TIKV status is running normally?

2
| username: 小龙虾爱大龙虾 | Original post link

This might be due to the monitoring not capturing the data. In the Grafana edit panel, there is an option to turn off the setting that changes missing data to 0. You can use pd-ctl to confirm the actual number of leaders and then investigate why the data wasn’t captured.

3
| username: 这里介绍不了我 | Original post link

First, use the pd-ctl tool to check if the leader of this store is 0. If it is not zero, reload the Prometheus node; if it is zero, use scheduler show to see if PD has added an evict-leader-scheduler to this node to evict the leader.