From 9fc29840a156b3cfcaf7093d7e7d7c451ee89d42 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 5 Jun 2026 17:49:59 +0800 Subject: [PATCH 1/3] Create empty translation PR From 53c648354ce5eed38f7896d8a6244b89754e4c54 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Fri, 5 Jun 2026 09:51:29 +0000 Subject: [PATCH 2/3] Auto-sync: Update English docs from Chinese PR Synced from: https://github.com/pingcap/docs-cn/pull/21676 Target PR: https://github.com/pingcap/docs/pull/23011 AI Provider: azure Co-authored-by: github-actions[bot] --- pd-recover.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/pd-recover.md b/pd-recover.md index bf15f80800f08..8466074acdb3d 100644 --- a/pd-recover.md +++ b/pd-recover.md @@ -39,6 +39,8 @@ Start the surviving PD node using the `--force-new-cluster` startup parameter, a ./bin/pd-server --force-new-cluster --name=pd-127.0.0.10-2379 --data-dir=/path/to/existing/pd/data --client-urls=http://0.0.0.0:2379 --advertise-client-urls=http://127.0.0.1:2379 --peer-urls=http://0.0.0.0:2380 --advertise-peer-urls=http://127.0.0.1:2380 --config=conf/pd.toml ``` +This command starts a temporary single-node PD, allowing `pd-recover` in the next step to connect and repair the metadata. Keep this PD process running, and perform the next step in another terminal window. + > **Note:** > > - If `--data-dir` is not specified in the command line, ensure that `data-dir` in `conf/pd.toml` correctly points to the original data directory of the surviving PD node. Otherwise `pd-recover` might fail in subsequent operations. @@ -60,11 +62,11 @@ Since this method relies on a minority PD node to recover the service, the node ### Step 4: Restart the PD node -Once you see the prompt message `recovery is successful`, restart the PD node. +Once you see the prompt message `recovery is successful`, stop the temporary PD process started with `--force-new-cluster` in Step 2, and then restart the PD node normally without the `--force-new-cluster` parameter. ### Step 5: Scale out PD and start the cluster -Scale out the PD cluster using the deployment tool and start the other components in the cluster. At this point, the PD service is available. +After confirming that the PD in Step 4 has started normally and is providing service, scale out the PD cluster using the deployment tool and start the other components in the cluster. At this point, the service is restored. ## Method 2: Entirely rebuild a PD cluster From 1d9f24040701194d2bf1984d75736f4cf6d70f17 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 5 Jun 2026 17:57:36 +0800 Subject: [PATCH 3/3] Update pd-recover.md --- pd-recover.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pd-recover.md b/pd-recover.md index 8466074acdb3d..020a81812c2d3 100644 --- a/pd-recover.md +++ b/pd-recover.md @@ -62,7 +62,7 @@ Since this method relies on a minority PD node to recover the service, the node ### Step 4: Restart the PD node -Once you see the prompt message `recovery is successful`, stop the temporary PD process started with `--force-new-cluster` in Step 2, and then restart the PD node normally without the `--force-new-cluster` parameter. +Once you see the prompt message `recovery is successful`, stop the temporary PD process that starts with `--force-new-cluster` in Step 2, and then restart the PD node normally without the `--force-new-cluster` parameter. ### Step 5: Scale out PD and start the cluster