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

log-backup: failed to truncate the log data on gcs or azure blob #38229

Closed
Leavrth opened this issue Sep 28, 2022 · 0 comments · Fixed by #38232
Closed

log-backup: failed to truncate the log data on gcs or azure blob #38229

Leavrth opened this issue Sep 28, 2022 · 0 comments · Fixed by #38232
Labels
component/br This issue is related to BR of TiDB. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@Leavrth
Copy link
Contributor

Leavrth commented Sep 28, 2022

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

do log truncate

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

truncate done.

3. What did you see instead (Required)

Error: failed during rewriting the file at v1_stream_trancate_safepoint.txt in azure://test/pitr-test-01: the origin file doesn't exist: [BR:Common:ErrInvalidArgument]invalid argument

4. What is your TiDB version? (Required)

nightly

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