pingcap / pingcap/tidb-operator
for a 100T cluster after restore, the QPS decreased and became unstable in the first two hours [restore for 5269]
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?
gcr.io/pingcap-public/dbaas/tikv:v6.5.4-20230822-1692700456
gcr.io/pingcap-public/dbaas/tidb:v6.5.4-20230822-1692700456
gcr.io/pingcap-public/dbaas/pd:v6.5.4-20230822-1692700456
gcr.io/pingcap-public/dbaas/br:v6.5.4-20230822-1692700456
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?
- do volumerestore(100T)
- add workload on restore cluster
What did you expect to see?
- the QPS of restore cluster is same with backup cluster
What did you see instead?
- the QPS decreased and became unstable in the first two hours
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.