We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please answer these questions before submitting your issue. Thanks!
Run full backup with --ratelimit is specified.
Backup job is run in serial
Confusing messages show in the output like
[2024/01/30 17:26:19.926 +08:00] [WARN] [logging.go:253] ["setting --ratelimitand--concurrencyat the same time, ignoring--concurrency: --ratelimit forces sequential (i.e. concurrency = 1) backup"] [ratelimit=134.2MB/s] [concurrency-specified=1] [2024/01/30 17:26:25.222 +08:00] [INFO] [client.go:874] ["backup range started"] [range-sn=0] [startKey=74800000000000010B5F7201] [endKey=74800000000000010B5F72FB] [rateLimit=134217728] [concurrency=4]
[2024/01/30 17:26:19.926 +08:00] [WARN] [logging.go:253] ["setting
and
at the same time, ignoring
:
forces sequential (i.e. concurrency = 1) backup"] [ratelimit=134.2MB/s] [concurrency-specified=1]
[2024/01/30 17:26:25.222 +08:00] [INFO] [client.go:874] ["backup range started"] [range-sn=0] [startKey=74800000000000010B5F7201] [endKey=74800000000000010B5F72FB] [rateLimit=134217728] [concurrency=4]
The text was updated successfully, but these errors were encountered:
/component br
Sorry, something went wrong.
/severity moderate
We need to remove the attribute of concurrency for the tikv pb request because it is never used.
br: remove misleading log info (#52145)
5f53c70
close #50837
Successfully merging a pull request may close this issue.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Run full backup with --ratelimit is specified.
2. What did you expect to see? (Required)
Backup job is run in serial
3. What did you see instead (Required)
Confusing messages show in the output like
[2024/01/30 17:26:19.926 +08:00] [WARN] [logging.go:253] ["setting
--ratelimitand
--concurrencyat the same time, ignoring
--concurrency:
--ratelimitforces sequential (i.e. concurrency = 1) backup"] [ratelimit=134.2MB/s] [concurrency-specified=1]
[2024/01/30 17:26:25.222 +08:00] [INFO] [client.go:874] ["backup range started"] [range-sn=0] [startKey=74800000000000010B5F7201] [endKey=74800000000000010B5F72FB] [rateLimit=134217728] [concurrency=4]
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: