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

When the CDC cannot connect downstream, the changefeed status is not set to error [restore for 4915] #11695

Open
ti-chi-bot opened this issue Oct 25, 2024 · 1 comment
Assignees
Labels
area/ticdc Issues or PRs related to TiCDC. type/bug The issue is confirmed as a bug.

Comments

@ti-chi-bot
Copy link
Member

What did you do?

  1. create vpc peering between kafka/mysql and tidb in dbaas
  2. create cdc changefeed between tidb and kafka/mysql
  3. delete vpc peering

What did you expect to see?

  1. When the CDC cannot connect downstream, the changefeed status should be set to error

What did you see instead?

the changefeed status is not set to error

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)
@ti-chi-bot ti-chi-bot added area/ticdc Issues or PRs related to TiCDC. type/bug The issue is confirmed as a bug. labels Oct 25, 2024
@ti-chi-bot
Copy link
Member Author

This issue is restored for #4915, it originally created at 2022-03-16 07:42:38.

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. type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

2 participants