Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

for a 100T cluster after restore, the QPS decreased and became unstable in the first two hours [restore for 5269] #5798

Open
ti-chi-bot opened this issue Oct 25, 2024 · 1 comment
Assignees
Labels
area/ebs-br type/bug Something isn't working

Comments

@ti-chi-bot
Copy link
Member

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?

  1. do volumerestore(100T)
  2. add workload on restore cluster

What did you expect to see?

  1. the QPS of restore cluster is same with backup cluster

What did you see instead?

  1. the QPS decreased and became unstable in the first two hours
    image
@ti-chi-bot ti-chi-bot added area/ebs-br type/bug Something isn't working labels Oct 25, 2024
@ti-chi-bot
Copy link
Member Author

This issue is restored for #5269, it originally created at 2023-08-25 03:25:24.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ebs-br type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants