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

Owner exits unexpectedly due to emit checkpoint failure #1902

Closed
overvenus opened this issue Jun 1, 2021 · 1 comment
Closed

Owner exits unexpectedly due to emit checkpoint failure #1902

overvenus opened this issue Jun 1, 2021 · 1 comment
Assignees
Labels
area/ticdc Issues or PRs related to TiCDC. bug-from-user Bugs found by users. component/scheduler TiCDC inner scheduler component. severity/major type/bug The issue is confirmed as a bug.

Comments

@overvenus
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do? If possible, provide a recipe for reproducing the error.

Owner exits unexpectedly due to emit checkpoint failure.

[2021/05/31 11:55:02.228 +00:00] [WARN] [server.go:188] ["run owner failed"] [error="[CDC:ErrKafkaSendMessage]kafka: Failed to deliver 1 messages."] [errorVerbose="[CDC:ErrKafkaSendMessage]kafka: Failed to deliver 1 messages.
github.com/pingcap/errors.AddStack
	github.com/pingcap/errors@v0.11.5-0.20201126102027-b0a155152ca3/errors.go:174
github.com/pingcap/errors.(*Error).GenWithStackByCause
	github.com/pingcap/errors@v0.11.5-0.20201126102027-b0a155152ca3/normalize.go:279
github.com/pingcap/ticdc/pkg/errors.WrapError
	github.com/pingcap/ticdc@/pkg/errors/helper.go:28
github.com/pingcap/ticdc/cdc/sink/producer/kafka.(*kafkaSaramaProducer).SyncBroadcastMessage
	github.com/pingcap/ticdc@/cdc/sink/producer/kafka/kafka.go:142
github.com/pingcap/ticdc/cdc/sink.(*mqSink).writeToProducer
	github.com/pingcap/ticdc@/cdc/sink/mq.go:381
github.com/pingcap/ticdc/cdc/sink.(*mqSink).EmitCheckpointTs
	github.com/pingcap/ticdc@/cdc/sink/mq.go:234
github.com/pingcap/ticdc/cdc.(*changeFeed).calcResolvedTs
	github.com/pingcap/ticdc@/cdc/changefeed.go:939
github.com/pingcap/ticdc/cdc.(*Owner).calcResolvedTs
	github.com/pingcap/ticdc@/cdc/owner.go:800
github.com/pingcap/ticdc/cdc.(*Owner).run
	github.com/pingcap/ticdc@/cdc/owner.go:1334
github.com/pingcap/ticdc/cdc.(*Owner).Run
	github.com/pingcap/ticdc@/cdc/owner.go:1204
github.com/pingcap/ticdc/cdc.(*Server).campaignOwnerLoop
	github.com/pingcap/ticdc@/cdc/server.go:172
github.com/pingcap/ticdc/cdc.(*Server).run.func1
	github.com/pingcap/ticdc@/cdc/server.go:255
golang.org/x/sync/errgroup.(*Group).Go.func1
	golang.org/x/sync@v0.0.0-20201020160332-67f06af15bc9/errgroup/errgroup.go:57
runtime.goexit
	runtime/asm_amd64.s:1357"]
  1. What did you expect to see?

TiCDC owner should not stop.

  1. What did you see instead?

TiCDC owner stops.

  1. Versions of the cluster

v5.0.1

@3AceShowHand
Copy link
Contributor

it's fixed in #1985

@AkiraXie AkiraXie added the area/ticdc Issues or PRs related to TiCDC. label Mar 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ticdc Issues or PRs related to TiCDC. bug-from-user Bugs found by users. component/scheduler TiCDC inner scheduler component. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

4 participants