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

cdc panic on the upstream manager #9915

Closed
3AceShowHand opened this issue Oct 17, 2023 · 1 comment · Fixed by #9917
Closed

cdc panic on the upstream manager #9915

3AceShowHand opened this issue Oct 17, 2023 · 1 comment · Fixed by #9917
Labels
affects-6.5 affects-7.1 affects-7.5 area/ticdc Issues or PRs related to TiCDC. needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@3AceShowHand
Copy link
Contributor

What did you do?

run the changefeed normally

What did you expect to see?

nothing

What did you see instead?

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x2d154b7]

goroutine 135 [running]:
github.com/pingcap/tiflow/pkg/upstream.(*Manager).Tick(0xc000ba2fc0, {0x7f277863e980, 0xc00137c0a0}, 0xc000b89260)
	github.com/pingcap/tiflow/pkg/upstream/manager.go:200 +0x1f7
github.com/pingcap/tiflow/cdc/processor.(*managerImpl).Tick(0xc0008c6d40, {0x7f277863e980?, 0xc00137c0a0}, {0x4307890?, 0xc000b89260})
	github.com/pingcap/tiflow/cdc/processor/manager.go:149 +0x585
github.com/pingcap/tiflow/pkg/orchestrator.(*EtcdWorker).Run(0xc002ec49a0, {0x7f277863e980, 0xc00137c0a0}, 0xc000b9c480, 0x2faf080, {0x39e726d, 0x9})
	github.com/pingcap/tiflow/pkg/orchestrator/etcd_worker.go:290 +0xfa6
github.com/pingcap/tiflow/cdc/capture.(*captureImpl).runEtcdWorker(0xc0018f5560, {0x432f290?, 0xc00137c0a0}, {0x7f2778a5d3a0, 0xc0008c6d40}, {0x4307890, 0xc000b89260}, 0xc002ea1788?, {0x39e726d, 0x9})
	github.com/pingcap/tiflow/cdc/capture/capture.go:550 +0x185
github.com/pingcap/tiflow/cdc/capture.(*captureImpl).run.func4()
	github.com/pingcap/tiflow/cdc/capture/capture.go:382 +0x3a5
golang.org/x/sync/errgroup.(*Group).Go.func1()
	golang.org/x/sync@v0.1.0/errgroup/errgroup.go:75 +0x64
created by golang.org/x/sync/errgroup.(*Group).Go
	golang.org/x/sync@v0.1.0/errgroup/errgroup.go:72 +0xa5
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x2d154b7]

Versions of the cluster

Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):

(paste TiDB cluster version here)

Upstream TiKV version (execute tikv-server --version):

(paste TiKV version here)

TiCDC version (execute cdc version):

v6.5.5
@nongfushanquan
Copy link
Contributor

/label affects-7.5

@3AceShowHand 3AceShowHand added affects-6.5 affects-7.1 needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. and removed type/cherry-pick-for-release-6.5 This PR is cherry-picked to release-6.5 from a source PR. type/cherry-pick-for-release-7.1 This PR is cherry-picked to release-7.1 from a source PR. type/cherry-pick-for-release-7.5 This PR is cherry-picked to release-7.5 from a source PR. labels Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.5 affects-7.1 affects-7.5 area/ticdc Issues or PRs related to TiCDC. needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. severity/moderate type/bug The issue is confirmed as a bug.
Projects
Development

Successfully merging a pull request may close this issue.

2 participants