-
Notifications
You must be signed in to change notification settings - Fork 276
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
[Bug]: dup and w-w during sysbench write_only case and tpcc test #14880
Comments
Dup produced by CN had been fixed! |
Latest main branch produced again, being fix. |
目前只在长期分布式稳定性中出现 |
Not working on this |
Not working on this |
原因如下: 1. txn1 在CN1 上insert 了 一条 PK, 并committed. 2. CN2 上的txn2 还未等到 这个pk 同步到partition state 中,就开始 运行 delete pk(delete statment 的snapshot ts 应该是小于txn1 的commit ts 的, 否则CN2 会等water mark 超过txn1 的commit ts ) , 这时pk 的rowid 查不到,delete 运行之后,affected rows =0, 相当于delete 没起效果; 然后运行 insert pk , 去重时,之前被txn1 提交的pk 同步过来了,然后在partiton state 中发现了相同的pk , 导致dup. |
#15992 fixed dup/ww bug. |
wait for @ouyuanning 's pr |
1 similar comment
wait for @ouyuanning 's pr |
Wait for PR merge |
@aressu1985 已知 的 dup/ww 都已经fix 了, 请测试观察. 远宁那个 delete 加锁问题导致 的dup/ww 有对应的issue. |
testing |
分支回归测试会有问题,还没时间处理 |
未投入 |
未投入 |
7 similar comments
未投入 |
未投入 |
未投入 |
未投入 |
未投入 |
未投入 |
未投入 |
先处理DML重构 |
1 similar comment
先处理DML重构 |
Is there an existing issue for the same bug?
Branch Name
1.1-dev
Commit ID
01fa016
Other Environment Information
Actual Behavior
job link:
https://github.com/matrixorigin/mo-nightly-regression/actions/runs/8210572569/job/22458565541
mo-log:
http://175.178.192.213:30088/explore?panes=%7B%22DWZ%22:%7B%22datasource%22:%22loki%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22expr%22:%22%7Bnamespace%3D%5C%22branch-reg-01fa016%5C%22%7D%20%7C%3D%20%60Duplicate%20entry%60%22,%22queryType%22:%22range%22,%22datasource%22:%7B%22type%22:%22loki%22,%22uid%22:%22loki%22%7D,%22editorMode%22:%22builder%22%7D%5D,%22range%22:%7B%22from%22:%221709964129691%22,%22to%22:%221710005409691%22%7D%7D%7D&schemaVersion=1&orgId=1
Expected Behavior
No response
Steps to Reproduce
Additional information
No response
The text was updated successfully, but these errors were encountered: