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

Data consistency when replicting tpcc workload to mysql sink #11343

Closed
fubinzh opened this issue Jun 25, 2024 · 3 comments
Closed

Data consistency when replicting tpcc workload to mysql sink #11343

fubinzh opened this issue Jun 25, 2024 · 3 comments
Assignees
Labels
area/ticdc Issues or PRs related to TiCDC. severity/critical This is a critical bug. type/bug This is a bug.

Comments

@fubinzh
Copy link

fubinzh commented Jun 25, 2024

What did you do?

  1. Upstream: TiDB cluster with 1 cdc node; CDC downstream: MySQL
  2. Create mysql sink changefeed
  3. Run tpcc workload
/go-tpc tpcc --db workload --warehouses 1000 -T 32 --host upstream-tidb.cdc-testbed-tps-7593068-1-644 --port 4000 --parts 1 prepare --ignore-error '2013,1213,1105,1205,8022,8028,9004,9007,1062'
/go-tpc tpcc --db workload --warehouses 1000 -T 32 --host upstream-tidb.cdc-testbed-tps-7593068-1-644 --port 4000 --parts 1 --time 5h0m0s run --ignore-error '2013,1213,1105,1205,8022,8028,9004,9007,1062'
  1. Wait sync finished and do data consistency check between upstrem and downstream

What did you expect to see?

Data should be consistent

What did you see instead?

Data inconsistency, and cdc panic seen.
img_v3_02c6_e25fed1a-fce7-4390-9938-56b4931e386g

[2024/06/25 01:21:47.816 +00:00] [PANIC] [shared_region_worker.go:286] ["The CommitTs must be greater than the resolvedTs"] [EventType=COMMITTED] [CommitTs=450698541640712196] [resolvedTs=450698544943726600] [regionID=676] [stack="github.com/pingcap/tiflow/cdc/kv.handleEventEntry\n\tgithub.com/pingcap/tiflow/cdc/kv/shared_region_worker.go:286\ngithub.com/pingcap/tiflow/cdc/kv.(*sharedRegionWorker).handleEventEntry\n\tgithub.com/pingcap/tiflow/cdc/kv/shared_region_worker.go:237\ngithub.com/pingcap/tiflow/cdc/kv.(*sharedRegionWorker).processEvent\n\tgithub.com/pingcap/tiflow/cdc/kv/shared_region_worker.go:197\ngithub.com/pingcap/tiflow/cdc/kv.(*sharedRegionWorker).run\n\tgithub.com/pingcap/tiflow/cdc/kv/shared_region_worker.go:164\ngithub.com/pingcap/tiflow/cdc/kv.(*SharedClient).Run.func1\n\tgithub.com/pingcap/tiflow/cdc/kv/shared_client.go:346\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/[email protected]/errgroup/errgroup.go:78"]

Versions of the cluster

Release Version: v8.2.0-alpha
Git Commit Hash: c001638
Git Branch: heads/refs/tags/v8.2.0-alpha
UTC Build Time: 2024-06-21 11:36:49
Go Version: go version go1.21.10 linux/amd64
Failpoint Build: false

@fubinzh fubinzh added area/ticdc Issues or PRs related to TiCDC. type/bug This is a bug. labels Jun 25, 2024
@github-actions github-actions bot added this to Need Triage in Question and Bug Reports Jun 25, 2024
@fubinzh
Copy link
Author

fubinzh commented Jun 25, 2024

/severity critical

@hicqu
Copy link
Contributor

hicqu commented Jul 4, 2024

Duplicated with tikv/tikv#17233.

@hicqu hicqu closed this as completed Jul 4, 2024
Question and Bug Reports automation moved this from Need Triage to Done Jul 4, 2024
@flowbehappy
Copy link
Collaborator

Remove the affected versions, as we use another issues to track.

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. severity/critical This is a critical bug. type/bug This is a bug.
Development

No branches or pull requests

5 participants