Different TiUP central deploy TiDB cluster on the same host directory will overwritten data
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Feature Request
Is your feature request related to a problem? Please describe:
I use different TiUP central deploy TiDB cluster on the same host directory.
Data from the first deployment will be overwritten by data from the second deployment
When I destroy one cluster, both clusters will destroy.
Describe the feature you'd like:
When using different TiUP central deploy TiDB cluster on the same host could give a note.
Let us know maybe we make a mistake.
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
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
No file, test, or entry point is named. Start by reproducing two TiUP central deployments of TiDB clusters in the same host directory, then trace the deployment and destroy flows that select cluster data paths. Done means the conflicting-directory case is detected and users receive a clear warning before data can be overwritten or both clusters destroyed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100