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.

Sign up for GitHub

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

Jump to bottom

br: when running 1m-tables workload, restore data to log backup on cluster would lower qps a lot #58800

Open
AkiraXie opened this issue Jan 8, 2025 · 2 comments
Open

br: when running 1m-tables workload, restore data to log backup on cluster would lower qps a lot #58800

AkiraXie opened this issue Jan 8, 2025 · 2 comments
Labels
component/br This issue is related to BR of TiDB. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/major type/bug The issue is confirmed as a bug.

Comments

@AkiraXie
Copy link

AkiraXie commented Jan 8, 2025 •
edited
Loading

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. open log backup
  2. run 1m-tables workload
  3. restore 500k row-wide data to cluster using br built from br: copy full backup to pitr storage #57716

2. What did you expect to see? (Required)

restore ok , and it applied little impact on cluster

3. What did you see instead (Required)

restore ok
[2025/01/08 09:28:02.878 +00:00] [INFO] [collector.go:77] ["Full Restore success summary"] [total-ranges=1902] [ranges-succeed=1902] [ranges-failed=0] [restore-ranges=951] [total-take=27m13.135616731s] [restore-data-size(after-compressed)=177.1GB] [Size=177070222932] [BackupTS=454975490842427393] [RestoreTS=455167685949915391] [total-kv=3000000] [total-kv-size=240.8GB] [average-speed=147.4MB/s]

but qps is lower a lot
Image
Image

4. What is your TiDB version? (Required)

master
@AkiraXie AkiraXie added the type/bug The issue is confirmed as a bug. label Jan 8, 2025
@AkiraXie
Copy link
Author

AkiraXie commented Jan 8, 2025

/component br
/severity critical

@AkiraXie
Copy link
Author

AkiraXie commented Jan 8, 2025

/severity major
/remove-severity critical

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/br This issue is related to BR of TiDB. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AkiraXie