Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lag of steps to do pd recover on tiup #10244

Open
Jingyuma opened this issue Aug 26, 2022 · 2 comments
Open

lag of steps to do pd recover on tiup #10244

Jingyuma opened this issue Aug 26, 2022 · 2 comments
Labels
area/scheduling Indicates that the Issue or PR belongs to the area of scheduling. tracked This issue has been tracked.

Comments

@Jingyuma
Copy link

File: /release-6.1/pd-recover.md

Before clean the data dir, also need to delete other PD endpoint from startup script.

Or the startup of PD will be failed, and PD recover will failed to connect to PD too.

So people follow the guide will failed to run pd recover.

@shichun-0415 shichun-0415 added the area/scheduling Indicates that the Issue or PR belongs to the area of scheduling. label Aug 27, 2022
@shichun-0415
Copy link
Contributor

@Jingyuma Thanks for the feedback. @bufferflies Could you help take a look at this issue. Thanks.

@Oreoxmt Oreoxmt added the tracked This issue has been tracked. label Feb 15, 2023
@CabinfeverB
Copy link
Contributor

IMO,

Before deploying a new PD cluster, you need to stop the the existing PD cluster and then delete the previous data directory or specify a new data directory using --data-dir.
It means u deploying a new PD cluster with new endpoints, and if u delete the previous data directory, u should delete all pd data dir.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/scheduling Indicates that the Issue or PR belongs to the area of scheduling. tracked This issue has been tracked.
Projects
None yet
Development

No branches or pull requests

4 participants