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

changefeed cannot replicate DMLs in BDR mode if the targeted table is dropped and then re-created in the upstream. #10079

Closed
asddongmen opened this issue Nov 10, 2023 · 0 comments · Fixed by #10080
Assignees
Labels
affects-6.5 affects-7.1 affects-7.5 area/ticdc Issues or PRs related to TiCDC. severity/major type/bug The issue is confirmed as a bug.

Comments

@asddongmen
Copy link
Contributor

What did you do?

  1. Create tables t1, t2, and t3 in the upstream and downstream.
  2. Create a changefeed and enable BDR mode to sync data from the source to the target.
  3. Insert data into t1, and the sync proceeds normally.
  4. Drop table t2.
  5. Continue inserting data into t1 and t3, and the sync proceeds normally (dropping t2 does not affect t1).
  6. Drop table t1.
  7. Create table t1.
  8. Insert data into t1, but unable to sync properly.
  9. Insert data into t3, and the sync proceeds normally (dropping t1 does not affect t3).
  10. Pause and resume the changefeed to restore normal sync.

What did you expect to see?

No response

What did you see instead?

DMLs should be syned.

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):

master
@asddongmen asddongmen added type/bug The issue is confirmed as a bug. severity/moderate area/ticdc Issues or PRs related to TiCDC. affects-6.5 affects-7.1 affects-7.5 labels Nov 10, 2023
@asddongmen asddongmen self-assigned this Nov 10, 2023
ti-chi-bot bot pushed a commit that referenced this issue Nov 14, 2023
ti-chi-bot bot pushed a commit that referenced this issue Nov 15, 2023
ti-chi-bot bot pushed a commit that referenced this issue Nov 20, 2023
ti-chi-bot bot pushed a commit that referenced this issue Dec 6, 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. severity/major type/bug The issue is confirmed as a bug.
Projects
1 participant