pingcap / pingcap/tidb-operator
it is recommended to check the number of tikv volumes when restoring [restore for 5287]
Open
@BornChanger is already working on this.
Since Oct 25, 2024.
area/ebs-br
type/bug
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Bug Report
What version of Kubernetes are you using?
What version of TiDB Operator are you using?
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
What's the status of the TiDB cluster pods?
What did you do?
- create a cluster with 3 tikvs，each tikv has 1 volume
- do volumebackup
- do volumerestore, restore cluster also has 3 tikvs, but tikv has 4 volumes
What did you expect to see?
- there is a precheck when user do volumerestore
What did you see instead?
- there is no precheck when user do volumerestore, and warmup pod can not be started, user can not see error message in volumerestore/restore crd, the volumerestore/restore status is running
- the error message only can be see in operator log
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.
Assessment
This issue has not been assessed yet.