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

Error: unexpected end of JSON input when restore #36379

Open
D3Hunter opened this issue Jul 20, 2022 · 2 comments
Open

Error: unexpected end of JSON input when restore #36379

D3Hunter opened this issue Jul 20, 2022 · 2 comments
Labels
component/br This issue is related to BR of TiDB. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@D3Hunter
Copy link
Contributor

D3Hunter commented Jul 20, 2022

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. use nightly BR to full backup nightly tidb
    • or use 6.1.0 BR to backup 6.1.0 tidb, restore will fail with same error
  2. use 6.0.0 BR to full restore 6.0.0 tidb

log
backup.log
restore.log

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

success

3. What did you see instead (Required)

[2022/07/20 19:20:59.556 +08:00] [INFO] [collector.go:67] ["Full Restore failed summary"] [total-ranges=0] [ranges-succeed=0] [ranges-failed=0]
Error: unexpected end of JSON input

4. What is your TiDB version? (Required)

@D3Hunter D3Hunter added type/bug The issue is confirmed as a bug. component/br This issue is related to BR of TiDB. labels Jul 20, 2022
@fubinzh
Copy link

fubinzh commented Jul 22, 2022

Per Dev, below scenarios are impacted:
Use br nightly to backup nightly cluster, then use br 6.0 to restore to 6.0 cluster.
Use br 6.1 to backup nightly cluster, then use br 6.0 to restore to 6.0 cluster.
Use br nightly to backup nightly cluster, then use br 5.4 to restore to 5.4 cluster.

Below scenarios are not impacted:
Use br nightly to backup nightly cluster, then use br nightly to restore to nightly cluster.

@D3Hunter
Copy link
Contributor Author

it's caused by empty database in backup data. can workaround by using explicit filter

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

No branches or pull requests

2 participants