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.

Sign up for GitHub

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

Jump to bottom

data inconsistency after inject kill all cdc chaos #11219

Closed
Lily2025 opened this issue May 31, 2024 · 6 comments · Fixed by #11296
Closed

data inconsistency after inject kill all cdc chaos #11219

Lily2025 opened this issue May 31, 2024 · 6 comments · Fixed by #11296
Assignees
@sdojjy @asddongmen @lidezhu @CharlesCheung96
Labels
affects-6.5 affects-7.1 affects-7.5 affects-8.1 area/ticdc Issues or PRs related to TiCDC. bug-from-internal-test Bugs found by internal testing. severity/critical type/bug The issue is confirmed as a bug.

Comments

@Lily2025
Copy link

What did you do?

1、create BDR cluster
task1：tc->cdc-downstream，run workload for sysbench_64_7000w
task2：cdc-downstream->tc，run workload for test

2、inject some fault to upstream and downstream
img_v3_02bd_60e1f6aa-10d5-4f8b-babe-313923f701fg

3、stop workload

4、compare data between upstream and downstream

What did you expect to see?

the data is consistent

What did you see instead?

data inconsistency after inject some fault to BDR cluster

img_v3_02bd_a1458a25-bcf8-4be9-81c8-6c7a32256b5g

Versions of the cluster

./cdc version
Release Version: v7.5.2
Git Commit Hash: 3625884
Git Branch: HEAD
UTC Build Time: 2024-05-30 09:00:27
Go Version: go version go1.21.10 linux/amd64
Failpoint Build: false
2024-05-31T13:10:18.390+0800

current status of DM cluster (execute query-status <task-name> in dmctl)

No response
@Lily2025 Lily2025 added area/dm Issues or PRs related to DM. type/bug The issue is confirmed as a bug. labels May 31, 2024
@Lily2025
Copy link
Author

/remove-area dm
/area ticdc
/assign asddongmen

@ti-chi-bot ti-chi-bot bot added area/ticdc Issues or PRs related to TiCDC. and removed area/dm Issues or PRs related to DM. labels May 31, 2024
@Lily2025
Copy link
Author

Lily2025 commented Jun 3, 2024

/severity critical

@jebter
Copy link

jebter commented Jun 4, 2024

/type regression

@jebter
Copy link

jebter commented Jun 4, 2024

/remove-type regression

@Ivy-YinSu Ivy-YinSu mentioned this issue Jun 6, 2024
Closed
11 tasks
@lidezhu lidezhu mentioned this issue Jun 7, 2024
Merged
@asddongmen asddongmen changed the title data inconsistency after inject some fault to BDR cluster data inconsistency after inject kill all cdc chaos Jun 7, 2024
@asddongmen asddongmen added the bug-from-internal-test Bugs found by internal testing. label Jun 7, 2024
ti-chi-bot bot pushed a commit that referenced this issue Jun 7, 2024
@lidezhu
puller(ticdc): fix wrong update splitting behavior after table schedu…
7c968ee 
…ling (#11269)

close #11219
This was referenced Jun 11, 2024
Merged
Merged
Merged
ti-chi-bot bot pushed a commit that referenced this issue Jun 11, 2024
@ti-chi-bot
puller(ticdc): fix wrong update splitting behavior after table schedu…
3426e46 
…ling (#11269) (#11282)

close #11219
ti-chi-bot bot pushed a commit that referenced this issue Jun 11, 2024
@ti-chi-bot
puller(ticdc): fix wrong update splitting behavior after table schedu…
f203805 
…ling (#11269) (#11281)

close #11219
ti-chi-bot bot pushed a commit that referenced this issue Jun 11, 2024
@ti-chi-bot
puller(ticdc): fix wrong update splitting behavior after table schedu…
20ee93f 
…ling (#11269) (#11283)

close #11219
lidezhu pushed a commit to lidezhu/tiflow that referenced this issue Jun 11, 2024
@ti-chi-bot @lidezhu
puller(ticdc): fix wrong update splitting behavior after table schedu…
f25075d 
…ling (pingcap#11269) (pingcap#11283)

close pingcap#11219
@lidezhu lidezhu mentioned this issue Jun 11, 2024
Merged
hicqu added a commit to ti-chi-bot/tiflow that referenced this issue Jun 12, 2024
@hicqu
Squashed commit of the following:
a3d30ca 
commit c092599
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Wed Jun 12 00:26:59 2024 +0800

    pkg/config, sink(ticdc): support output raw change event for mq and cloud storage sink (pingcap#11226) (pingcap#11290)

    close pingcap#11211

commit 3426e46
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Tue Jun 11 19:40:29 2024 +0800

    puller(ticdc): fix wrong update splitting behavior after table scheduling (pingcap#11269) (pingcap#11282)

    close pingcap#11219

commit 2a28078
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Tue Jun 11 16:40:37 2024 +0800

    mysql(ticdc): remove error filter when check isTiDB in backend init (pingcap#11214) (pingcap#11261)

    close pingcap#11213

commit 2425d54
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Tue Jun 11 16:40:30 2024 +0800

    log(ticdc): Add more error query information to the returned error to facilitate users to know the cause of the failure (pingcap#10945) (pingcap#11257)

    close pingcap#11254

commit 053cdaf
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Tue Jun 11 15:34:30 2024 +0800

    cdc: log slow conflict detect every 60s (pingcap#11251) (pingcap#11287)

    close pingcap#11271

commit 327ba7b
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Tue Jun 11 11:42:00 2024 +0800

    redo(ticdc): return internal error in redo writer (pingcap#11011) (pingcap#11091)

    close pingcap#10124

commit d82ae89
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Mon Jun 10 22:28:29 2024 +0800

    ddl_puller (ticdc): handle dorp pk/uk ddl correctly (pingcap#10965) (pingcap#10981)

    close pingcap#10890

commit f15bec9
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Fri Jun 7 16:16:28 2024 +0800

    redo(ticdc): enable pprof and set memory limit for redo applier (pingcap#10904) (pingcap#10996)

    close pingcap#10900

commit ba50a0e
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Wed Jun 5 19:58:26 2024 +0800

    test(ticdc): enable sequence test (pingcap#11023) (pingcap#11037)

    close pingcap#11015

commit 94b9897
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Wed Jun 5 17:08:56 2024 +0800

    mounter(ticdc): timezone fill default value should also consider tz. (pingcap#10932) (pingcap#10946)

    close pingcap#10931

commit a912d33
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Wed Jun 5 10:49:25 2024 +0800

    mysql (ticdc): Improve the performance of the mysql sink by refining the transaction event batching logic (pingcap#10466) (pingcap#11242)

    close pingcap#11241

commit 6277d9a
Author: dongmen <20351731+asddongmen@users.noreply.github.com>
Date:   Wed May 29 20:13:22 2024 +0800

    kvClient (ticdc): revert e5999e3 to remove useless metrics (pingcap#11184)

    close pingcap#11073

commit 54e93ed
Author: dongmen <20351731+asddongmen@users.noreply.github.com>
Date:   Wed May 29 17:43:22 2024 +0800

    syncpoint (ticdc): make syncpoint support base64 encoded password (pingcap#11162)

    close pingcap#10516

commit 0ba9329
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Wed May 29 09:07:21 2024 +0800

    (redo)ticdc: fix the event orderliness in redo log (pingcap#11117) (pingcap#11180)

    close pingcap#11096

Signed-off-by: qupeng <qupeng@pingcap.com>
@ti-chi-bot ti-chi-bot bot closed this as completed in e3412d9 Jun 13, 2024
This was referenced Jun 13, 2024
Closed
Closed
Closed
Closed
@seiya-annie
Copy link

/found customer

@ti-chi-bot ti-chi-bot bot added the report/customer Customers have encountered this bug. label Jun 19, 2024
@seiya-annie
Copy link

/remove-found customer

@ti-chi-bot ti-chi-bot bot removed the report/customer Customers have encountered this bug. label Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sdojjy sdojjy

@asddongmen asddongmen

@lidezhu lidezhu

@CharlesCheung96 CharlesCheung96

Labels
affects-6.5 affects-7.1 affects-7.5 affects-8.1 area/ticdc Issues or PRs related to TiCDC. bug-from-internal-test Bugs found by internal testing. severity/critical type/bug The issue is confirmed as a bug.
Projects
Question and Bug Reports
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

puller(ticdc): fix wrong update splitting behavior after table scheduling lidezhu/tiflow
7 participants
@sdojjy @jebter @asddongmen @lidezhu @seiya-annie @CharlesCheung96 @Lily2025