-
Notifications
You must be signed in to change notification settings - Fork 288
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
[ticdc 5.3.0] tikv_scale_plan_tidb case fail: 1. cdc oom, 2. data inconsistency, 3. changefeed stuck #3503
Comments
upstream tidb: downstream tidb: almost 2:1 warehouse row count is the same, only columne w_ytd totally different. |
CDC OOM is similar to https://github.com/pingcap/ticdc/pull/3439, has merged to master and will be fixed in next releases. |
Note this is a workaround that reduces the probability of pingcap#3503, sink may still reports a checkpoint that larger than resolved ts, and may cause data lose and changefeed stuck. Signed-off-by: Neil Shen <overvenus@gmail.com>
#3540 has mitigated this issue, change to severity/major. |
This issue is resolved by https://github.com/pingcap/ticdc/pull/3540 and https://github.com/pingcap/ticdc/pull/3436 |
What did you do?
// create 1 changefeed, 3 cdc, 3 tikv
// run tpcc 100 warehouse prepare
// run tpcc run, meanwhile, scale cluster tikv from 3 -> 7, after 15m, scale in to 3
// create table "finishmark"
// wait table "finishmark" sync to downstream
//check data consistency
What did you expect to see?
pass
What did you see instead?
testbed saved for 24 hours.
upstream grafana: http://172.16.4.180:30687/
testbed: cdc-testbed--tps-450050-1-772
conprof: http://172.16.4.180:30857/?query=%7Bnamespace%3D%22cdc-testbed--tps-450050-1-772%22%2C+job%3D%22ticdc%22%2C+profile_path%3D%22%2Fdebug%2Fpprof%2Fheap%22%7D&from=1637135181536&to=1637135672266&now=false
test case log: http://172.16.4.180:31714/workflows/testground/plan-exec-450050?tab=workflow&nodeId=plan-exec-450050-3513432500&sidePanel=logs
Versions of the cluster
Upstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):TiCDC version (execute
cdc version
):The text was updated successfully, but these errors were encountered: