Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: TiDB 备份时 SST 文件大小为 0
[TiDB Usage Environment] Production Environment
[TiDB Version] v6.5.0
[Reproduction Path] What operations were performed when the issue occurred
Using BR for backup, the SST files in the backup folder are 0 in size.
Here, S3 is used to mount the local directory, and all TiKV nodes have the same directory mounted. Both backup and restore operations should be performed in the same directory.
Could someone please advise if it is normal for the SST files to be 0 in size?
Is there any abnormal operation with br?
There were no exceptions reported during the backup, but an error occurs during the restore. Cannot read /xxx/xxx/2023-04-19-14-14/1/3536_221_289dc87df641c0306147a6bd6679eeb9cc6aac71f43c90989c87ff7bbf0b4646_1681884920819_default.sst
Take a look at the logs during the backup.
The backup using BR 7.0 was restored on a 6.5 cluster, and the logs indicate that it is not supported.
detected the old version of TiDB cluster, require: >= 6.6.0, but got 6.5.0"] [errorVerbose="detected the old version of TiDB cluster, require: >= 6.6.0, but got 6.5.0\
[2023/04/19 14:21:04.504 +08:00] [WARN] [restore.go:435] ["Keyspace BR is not supported in this cluster, fallback to legacy restore"] [error="detected the old version of tidb cluster, require: >= 6.6.0, but got 6.5.0"] [errorVerbose="detected the old version of tidb cluster, require: >= 6.6.0, but got 6.5.0\ngithub.com/pingcap/tidb/br/pkg/version.CheckVersionForKeyspaceBR\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/version/version.go:177\ngithub.com/pingcap/tidb/br/pkg/version.CheckClusterVersion\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/version/version.go:108\ngithub.com/pingcap/tidb/br/pkg/restore.CheckKeyspaceBREnable\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/restore/client.go:2897\ngithub.com/pingcap/tidb/br/pkg/task.configureRestoreClient\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/task/restore.go:433\ngithub.com/pingcap/tidb/br/pkg/task.runRestore\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/task/restore.go:570\ngithub.com/pingcap/tidb/br/pkg/task.RunRestore\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/task/restore.go:533\nmain.runRestoreCommand\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/cmd/br/restore.go:63\nmain.newFullRestoreCommand.func1\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/cmd/br/restore.go:148\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:916\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968\nmain.main\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/cmd/br/main.go:57\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1598"]
I just reinstalled br and switched to v6.5.0. After backing up and restoring again, there is still an issue with the sst file.
backup-202304191653.log (2.1 MB)
Normally, there should only be one SST file with the same name in a backup. I have two with the same name. 
If the same name appears twice, that is definitely not normal.
Check if there is an issue with S3.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: myzz
|
username: 
|
username: 
|
username: