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 point failed with restored-ts "2022-07-16 20:30:09.068 +0800 CST" which is from log metadata output #36370

Closed
fubinzh opened this issue Jul 20, 2022 · 0 comments · Fixed by #36369
Labels
component/br This issue is related to BR of TiDB. feature/developing the related feature is in development severity/moderate type/bug The issue is confirmed as a bug.

Comments

@fubinzh
Copy link

fubinzh commented Jul 20, 2022

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. Run log backup
  2. Run log metadata to get the range that can be recovered
[2022/07/16 21:38:18.047 +08:00] [INFO] [collector.go:69] ["log metadata"] [log-min-ts=434606285735330080] [log-min-date="2022-07-15 21:23:29.818 +0800 CST"] [log-max-ts=434628095919522279] [log-max-date="2022-07-16 20:30:09.068 +0800 CST"]

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

Restore should succeed

3. What did you see instead (Required)

Restore failed

tiup br:nightly log truncate -s "s3://xxx" --until "2022-07-16 20:30:09.068 +0800 CST"
...
Detail BR log in /tmp/br.log.2022-07-16T21.49.11+0800
Error: must set timezone when using datetime format ts

4. What is your TiDB version? (Required)

6.2 nightly

@fubinzh fubinzh added type/bug The issue is confirmed as a bug. severity/moderate component/br This issue is related to BR of TiDB. feature/developing the related feature is in development labels Jul 20, 2022
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. feature/developing the related feature is in development severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant