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 cluster open log backup, restore 500k+ tables often failed because of copy sst error #58748

Closed
AkiraXie opened this issue Jan 7, 2025 · 2 comments
Closed

br: when cluster open log backup, restore 500k+ tables often failed because of copy sst error #58748

AkiraXie opened this issue Jan 7, 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 7, 2025

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. use br: copy full backup to pitr storage #57716 build br
  2. cluster open log backup
  3. restore 500k+ tables to cluster

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

restore ok

3. What did you see instead (Required)

restore failed

Error: failed to execute the delaied callback #0: failed to put sst 1006/4192_256_598b83294414ab2dec14b72390014a7990f3d9ada05d0f5b485e0f6c64ce29c4_1736192310897_write.sst: RequestError: send request failed
caused by: Put "https://qe-testing.ks3-cn-beijing-internal.ksyuncs.com/kernel-testing/scenario/log2-0106/v1/ext_backups/backup-0650F65E09D8007F/sst_files/1006/4192_256_598b83294414ab2dec14b72390014a7990f3d9ada05d0f5b485e0f6c64ce29c4_1736192310897_write.sst": dial tcp 198.18.96.170:443: connect: connection refused

after failure, repeat restore process, restore would also fail because of similiar error

4. What is your TiDB version? (Required)

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

AkiraXie commented Jan 7, 2025

/component br
/severity major

@BornChanger
Copy link
Contributor

It's an problem caused by unstable network.

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
2 participants
@AkiraXie @BornChanger