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

Rows are lost for 100K table and go-ycsb workload test #4994

Closed
Tammyxia opened this issue Mar 23, 2022 · 3 comments
Closed

Rows are lost for 100K table and go-ycsb workload test #4994

Tammyxia opened this issue Mar 23, 2022 · 3 comments

Comments

@Tammyxia
Copy link

Tammyxia commented Mar 23, 2022

What did you do?

  • BR restore 100K source data to upstream and downstream TiDB cluster.
  • Create a changefeed, then run workload: go-ycsb load and run on table prefix unit2_.
  • Run test case with chaos: upstream all node restart, cdc owner switch, all upstream unavailable, PD leader switch.
  • Check data correctness between upstream and downstream TiDB cluster.

What did you expect to see?

Data consistency

What did you see instead?

image

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

TiKV
Release Version:   6.0.0-alpha
Edition:           Community
Git Commit Hash:   ac32d5c8099a85994a9790ae1840755033dd0fac
Git Commit Branch: heads/refs/tags/v6.1.0-nightly
UTC Build Time:    2022-03-21 23:16:34
Rust Version:      rustc 1.60.0-nightly (1e12aef3f 2022-02-13)
Enable Features:   jemalloc mem-profiling portable sse test-engines-rocksdb cloud-aws cloud-gcp cloud-azure
Profile:           dist_release

TiCDC version (execute cdc version):

(paste TiCDC version here)
elease Version: v5.4.0-master
Git Commit Hash: be5524dd90d5db245a22cc125599b5c81d78c2bb
Git Branch: heads/refs/tags/v6.1.0-nightly
UTC Build Time: 2022-03-21 23:15:49
Go Version: go version go1.18 linux/amd64
Failpoint Build: false
@Tammyxia
Copy link
Author

Reproduce again in this test.
image
image

@overvenus
Copy link
Member

It should be fixed by tikv/tikv#12262 let's keep it open and wait for another round of testing.

@overvenus
Copy link
Member

Can't reproduce again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants