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: when restore point with full backup and snapshot restore data, BR reports Fatal error #58819

Closed
AkiraXie opened this issue Jan 9, 2025 · 2 comments
Labels
affects-8.5 This bug affects the 8.5.x(LTS) versions. component/br This issue is related to BR of TiDB. feature/developing the related feature is in development may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 severity/critical type/bug The issue is confirmed as a bug.

Comments

@AkiraXie
Copy link

AkiraXie commented Jan 9, 2025

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

restore point with full backup and snapshot restore data

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

restore point is ok

3. What did you see instead (Required)

[2025/01/08 17:11:02.647 +00:00] [FATAL] [splitter.go:71] ["[unreachable] no table id matched"] [tableID=4358749] [stack="github.com/pingcap/tidb/br/pkg/restore/split.(*BaseSplitStrategy).GetAccumulations\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/restore/split/splitter.go:71\ngithub.com/pingcap/tidb/br/pkg/restore/log_client.(*LogClient).WrapCompactedFilesIterWithSplitHelper.(*PipelineRestorerWrapper[...]).WithSplit.func2\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/restore/restorer.go:366\ngithub.com/pingcap/tidb/br/pkg/utils/iter.tryMap[...].TryNext\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/utils/iter/combinator_types.go:140\ngithub.com/pingcap/tidb/br/pkg/restore/log_client.(*LogClient).RestoreCompactedSstFiles\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/restore/log_client/client.go:301\ngithub.com/pingcap/tidb/br/pkg/task.restoreStream.func6\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/task/stream.go:1566\ngithub.com/pingcap/tidb/br/pkg/task.withProgress\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/task/stream.go:1748\ngithub.com/pingcap/tidb/br/pkg/task.restoreStream\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/task/stream.go:1547\ngithub.com/pingcap/tidb/br/pkg/task.RunStreamRestore\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/task/stream.go:1311\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:721\nmain.runRestoreCommand\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/cmd/br/restore.go:80\nmain.newStreamRestoreCommand.func1\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/cmd/br/restore.go:254\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:1041\nmain.main\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/cmd/br/main.go:36\nruntime.main\n\t/go/pkg/mod/golang.org/[email protected]/src/runtime/proc.go:272"]

4. What is your TiDB version? (Required)

master

@AkiraXie AkiraXie added the type/bug The issue is confirmed as a bug. label Jan 9, 2025
@AkiraXie
Copy link
Author

AkiraXie commented Jan 9, 2025

/component br
/severity critical

@BornChanger BornChanger added the feature/developing the related feature is in development label Jan 13, 2025
@ti-chi-bot ti-chi-bot bot added affects-8.5 This bug affects the 8.5.x(LTS) versions. and removed may-affects-8.5 labels Jan 14, 2025
@YuJuncen
Copy link
Contributor

This is a problem during developing. No impact to master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-8.5 This bug affects the 8.5.x(LTS) versions. component/br This issue is related to BR of TiDB. feature/developing the related feature is in development may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 severity/critical type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

3 participants