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 download SST throughput not stable throughout the whole restore process #50593

Closed
Tracked by #50701
fubinzh opened this issue Jan 19, 2024 · 2 comments · Fixed by #51034
Closed
Tracked by #50701

Br restore download SST throughput not stable throughout the whole restore process #50593

fubinzh opened this issue Jan 19, 2024 · 2 comments · Fixed by #51034
Labels
component/br This issue is related to BR of TiDB. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@fubinzh
Copy link

fubinzh commented Jan 19, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. Run br restore to restore a cluster of 110TB

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

Download SST throughput should be use as much of the physical bandwidth as possible, and should be stable during the whole process.

3. What did you see instead (Required)

Download SST throughput can reach the disk throughtput limit (1200MB/s) sometime, but it is not stable enough, there are some downgrade to 1GB or lower.
image
image

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 19, 2024
@fubinzh
Copy link
Author

fubinzh commented Jan 19, 2024

/component br
/severity moderate

@3pointer
Copy link
Contributor

3pointer commented Feb 1, 2024

The issue is suspect it reach the grpc server limitaion: grpc-concurrent-stream which means handling the requests throughput in a stream. and the default value is 1024.

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

Successfully merging a pull request may close this issue.

2 participants