pingcap / pingcap/tidb-operator
When the backup commit ts of multiple k8s is inconsistent, it will cause the second phase of restore to be very slow [restore for 5109]
Open
@BornChanger is already working on this.
Since Oct 25, 2024.
- 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?
wangle1321/tidb-operator:202305261650
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
gp3(8000 iops 800 throughput)
What's the status of the TiDB cluster pods?
normal
What did you do?
1.create cluster(cross k8s)
2.do volumebackup(3 TiKVs, each 1.5 T volume, each tikv has 600 data), but three backup commit is is different
3. do volume restore
What did you expect to see?
- volume restore success and cost less than 1h
What did you see instead?
- The recovery has not been completed within 4 hours，Stuck in the raft 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.