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

br restore very slow (like it hangs) when merging files #50613

Closed
Tracked by #50701
fubinzh opened this issue Jan 21, 2024 · 3 comments · Fixed by #50648
Closed
Tracked by #50701

br restore very slow (like it hangs) when merging files #50613

fubinzh opened this issue Jan 21, 2024 · 3 comments · Fixed by #50648
Labels
affects-6.5 affects-7.1 affects-7.5 component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug.

Comments

@fubinzh
Copy link

fubinzh commented Jan 21, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. Run br restore full to restore a 300 TB cluster backup to a cluster with 100 TiKV nodes.

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

Restore should succeeds.

3. What did you see instead (Required)

Restore is very slow, it looks like it hangs when merging files. br restore doesn't enter "split and scatter phase" after ~40m of restore.

4. What is your TiDB version? (Required)

v7.6.0

@fubinzh fubinzh added the type/bug The issue is confirmed as a bug. label Jan 21, 2024
@fubinzh
Copy link
Author

fubinzh commented Jan 21, 2024

@fubinzh
Copy link
Author

fubinzh commented Jan 21, 2024

/component br

@3pointer
Copy link
Contributor

To workaround. we need skip merge files during restore

use --merge-region-key-count=1 to make merge skipped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.5 affects-7.1 affects-7.5 component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants