PD cannot detect KV node information

Translated
1

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

Original topic: PD检测不到KV节点信息

| username: lixiansheng

PD cannot detect the newly added TiKV resource information and cannot automatically transfer peers.

2
| username: wuxiangdong | Original post link

How about trying to manually migrate a region using pdctl?

3
| username: lixiansheng | Original post link

Manually it works. Additionally, I found that the store-id on the monitoring interface is different from the one queried in pd-ctl.

4
| username: lixiansheng | Original post link

No, it should be said that there is no information about the new node on the PD in the monitoring. This was first taken offline and then brought online, and the PD still remembers the original one.

5
| username: Kongdom | Original post link

Take a look at the top left corner, did the leader switch?

6
| username: lixiansheng | Original post link

The latest update: the two stores I added at the bottom of the screenshot have been there for more than two days, and only a few dozen peers have been balanced and migrated.

7
| username: lixiansheng | Original post link

Is it a scheduling limitation issue? I’ll try it first.

8
| username: wuxiangdong | Original post link

Has the scheduler for PD been removed or is it not functioning?

9
| username: tidb狂热爱好者 | Original post link

I see that his TiKV hasn’t started yet.

10
| username: h5n1 | Original post link

Check the display of the tiup cluster.