lag of steps to do pd recover on tiup
Open
Nobody has claimed this yet.
area/scheduling
tracked
- Dominant language
- Python
- Stars
- 617
- Forks
- 724
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 223
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open release-6.1/pd-recover.md and review the recovery steps around cleaning the data directory and the startup script. Document that other PD endpoints must be deleted from the startup script before cleaning the data directory, so PD can start and pd recover can connect successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100