After Replacing PD Completely, the TiKV Configuration File Still Contains Old PD Nodes

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

Original topic: PD 整体替换之后,TiKV 配置文件还存在老的 PD 节点

| username: Lei

[TiDB Usage Environment] Production Environment
[TiDB Version] 5.3
[Reproduction Path]
[Encountered Problem: Phenomenon and Impact]
During the cluster’s data center migration, in the final step, after using tiup to expand with 3 new PDs, switching the leader, and scaling down the old PDs, the run_tikv.sh script of TiKV still contains the offline PD nodes in the --pd parameter:
–pd “172.21.51.138:2379,10.64.2.19:2379,10.64.2.174:2379,10.64.2.17:2379”
The ps -ef|grep tikv command shows that the PD list still contains the old offline PDs.
What should I do now?

| username: h5n1 | Original post link

It doesn’t matter, it will change when TiKV restarts someday.

| username: tidb菜鸟一只 | Original post link

However, the old PD is no longer in your TiUP cluster configuration file. When you reload the TiKV nodes or restart the cluster, this run_tikv.sh will be overwritten with the new one.

| username: Fly-bird | Original post link

It will be gone after a restart.

| username: cassblanca | Original post link

Just reload