pingcap / pingcap/ticdc

pulsar consumer stuck after broker restarted

Open
#4,834 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component/test severity/moderate type/bug
Dominant language
Go
Stars
56
Forks
63
Avg merge
2d 20h
Merged PRs (30d)
34

Description

What did you do?

run Pulsar random broker failure test case

What did you expect to see?

No response

What did you see instead?

pulsar consumer stuck

[2026/04/15 07:42:22.460 +00:00] [INFO] [connection.go:257] ["Connecting to broker"] [remote_addr=pulsar://downstream-lb.cdc-testbed-tps-8116459-1-425:6650]
[2026/04/15 07:42:22.462 +00:00] [WARN] [connection.go:287] ["Failed to connect to broker."] [remote_addr=pulsar://downstream-lb.cdc-testbed-tps-8116459-1-425:6650] [error="dial tcp 10.105.103.57:6650: connect: connection refused"]
[2026/04/15 07:42:22.674 +00:00] [INFO] [connection.go:257] ["Connecting to broker"] [remote_addr=pulsar://downstream-lb.cdc-testbed-tps-8116459-1-425:6650]
[2026/04/15 07:42:22.675 +00:00] [WARN] [connection.go:287] ["Failed to connect to broker."] [remote_addr=pulsar://downstream-lb.cdc-testbed-tps-8116459-1-425:6650] [error="dial tcp 10.105.103.57:6650: connect: connection refused"]
[2026/04/15 07:42:23.145 +00:00] [INFO] [connection.go:257] ["Connecting to broker"] [remote_addr=pulsar://downstream-lb.cdc-testbed-tps-8116459-1-425:6650]
[2026/04/15 07:42:23.145 +00:00] [WARN] [connection.go:287] ["Failed to connect to broker."] [remote_addr=pulsar://downstream-lb.cdc-testbed-tps-8116459-1-425:6650] [error="dial tcp 10.105.103.57:6650: connect: connection refused"]
[2026/04/15 07:42:24.050 +00:00] [INFO] [connection.go:257] ["Connecting to broker"] [remote_addr=pulsar://downstream-lb.cdc-testbed-tps-8116459-1-425:6650]
[2026/04/15 07:42:24.051 +00:00] [INFO] [connection.go:295] ["TCP connection established"] [remote_addr=pulsar://downstream-lb.cdc-testbed-tps-8116459-1-425:6650] [local_addr=10.200.76.56:53886]
[2026/04/15 07:42:24.144 +00:00] [INFO] [connection.go:348] ["Connection is ready"] [remote_addr=pulsar://downstream-lb.cdc-testbed-tps-8116459-1-425:6650] [local_addr=10.200.76.56:53886]
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):

(paste TiCDC version here)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Pulsar random broker failure test case and follow the consumer connection logs around broker restart and reconnection. Confirm whether the consumer resumes consuming after the log reports "Connection is ready"; the issue does not name a source file or test, and cluster versions are still missing.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.