pingcap / pingcap/ticdc

Unstable test `random_drop_message`

Open
#2,670 0 comments 0 reactions 1 assignee View on GitHub

@hongyunyan is already working on this.

Since Oct 16, 2025.

can't reproduce ga-optional severity/minor type/bug
Dominant language
Go
Stars
56
Forks
63
Avg merge
2d 20h
Merged PRs (30d)
34

Description

link: https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Fticdc%2Fpull_cdc_mysql_integration_heavy/detail/pull_cdc_mysql_integration_heavy/4383/pipeline/388/

  1. maintainer ask dispatcher 246851790476395481311654354300970078885 move from cdc1-restart-1.log to other nodes.
  2. cdc1-restart-1.log remove dispatcher 246851790476395481311654354300970078885
  3. While maintainer don't receive the remove finish infomration from cdc1-restart-1.log, although maintainer repeated to send message to remove dispatcher 246851790476395481311654354300970078885 to cdc1-restart-1.log
  4. So the move operator can't finish, and the dispatcher can't continue to sync data.

While it's quite strange why maintainer can't receive the message about 246851790476395481311654354300970078885 status.

One possible reason is that these messages were dropped by the failpoint, but this is very unlikely.
Since this issue hasn't been reproduced, I'm putting it on hold for now.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.