Should prevent different clusters from reusing the same S3 bucket and root path
Open
@JaySon-Huang is already working on this.
Since Jun 19, 2023.
component/storage
type/enhancement
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
- Deploy a disagg-arch cluster with TiFlash WNs
- Load some data into cluster
- Destroy the cluster but not removing the data stored on S3
- Re-deploy a disagg-arch cluster with the very same s3.bucket and s3.root
- Load some data into cluster
2. What did you expect to see? (Required)
The re-deploy cluster should detect that there exist some data remained by different cluster. The tiflash node should reject the startup.
3. What did you see instead (Required)
The tiflash node starts normally. And later happen to S3 data lost
4. What is your TiFlash version? (Required)
master
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.