How to Migrate All PDs to New Machines in a TiDB 3.0.3 Cluster

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

Original topic: TiDB3.0.3集群怎么操作迁移所有pd到新机器上

| username: TiDBer_C33

【TiDB Usage Environment】Production Environment / Testing / PoC
【TiDB Version】3.0.3
【Encountered Problem: Problem Description and Impact】
We need to migrate a few machines that have all the PD components of the cluster. What operations should be used to migrate PD to the new machines and then decommission the old PD?

| username: 芮芮是产品 | Original post link

You can check how PD is started in systemctl, and then run that command on the other three computers.

| username: TiDBer_C33 | Original post link

Is it certain that specifying the old PD address for components like TiKV will not cause any issues?

| username: ShawnYan | Original post link

Establish an SSH connection to the new machine, then expand PD to the new machine, and finally shrink the PD on the old machine.

| username: TiDBer_C33 | Original post link

Will expanding and shrinking PD automatically update the configurations of TiKV and other components?

| username: Fly-bird | Original post link

Is this version worth upgrading?

| username: 普罗米修斯 | Original post link

Refer to the following steps for scaling operations. Adding a PD node will synchronize TiKV information.

| username: 普罗米修斯 | Original post link

You are still using a lower version and didn’t notice. This is the process for scaling in and out PD with a lower version of Ansible.

| username: TiDBer_C33 | Original post link

Okay, I’ll give it a try, thanks.

| username: Kongdom | Original post link

Use the scaling method.

| username: dba远航 | Original post link

First expand the new PD, then shrink the old PD.