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

[Bug]: dup and w-w during sysbench write_only case and tpcc test #14880

Closed
1 task done
aressu1985 opened this issue Mar 11, 2024 · 33 comments
Closed
1 task done

[Bug]: dup and w-w during sysbench write_only case and tpcc test #14880

aressu1985 opened this issue Mar 11, 2024 · 33 comments
Assignees
Labels
kind/bug Something isn't working severity/s0 Extreme impact: Cause the application to break down and seriously affect the use
Milestone

Comments

@aressu1985
Copy link
Contributor

Is there an existing issue for the same bug?

  • I have checked the existing issues.

Branch Name

1.1-dev

Commit ID

01fa016

Other Environment Information

- Hardware parameters:
  3*CN: 16C 64G
  1*DN: 16C 64G
  3*LOG: 4C 16G
- OS type:
- Others:

Actual Behavior

job link:
https://github.com/matrixorigin/mo-nightly-regression/actions/runs/8210572569/job/22458565541
image

image

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

1. run sysbench write only case on 1.1-dev

Additional information

No response

@aressu1985 aressu1985 added kind/bug Something isn't working needs-triage severity/s0 Extreme impact: Cause the application to break down and seriously affect the use labels Mar 11, 2024
@aressu1985 aressu1985 added this to the 1.1.0 milestone Mar 11, 2024
@sukki37 sukki37 modified the milestones: 1.1.0, 1.2.0 Mar 11, 2024
@triump2020
Copy link
Contributor

Dup produced by CN had been fixed!

@triump2020
Copy link
Contributor

Latest main branch produced again, being fix.

@triump2020
Copy link
Contributor

目前只在长期分布式稳定性中出现

@triump2020
Copy link
Contributor

#15235

@triump2020
Copy link
Contributor

Not working on this

@triump2020
Copy link
Contributor

#15545

@triump2020
Copy link
Contributor

Not working on this

@aressu1985 aressu1985 modified the milestones: 1.2.0, 1.3.0-Backlog Apr 24, 2024
@triump2020
Copy link
Contributor

原因如下: 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.

@triump2020
Copy link
Contributor

#15948

@triump2020
Copy link
Contributor

#15992 fixed dup/ww bug.

@triump2020
Copy link
Contributor

wait for @ouyuanning 's pr

1 similar comment
@triump2020
Copy link
Contributor

wait for @ouyuanning 's pr

@triump2020
Copy link
Contributor

Wait for PR merge

@triump2020
Copy link
Contributor

@aressu1985 已知 的 dup/ww 都已经fix 了, 请测试观察. 远宁那个 delete 加锁问题导致 的dup/ww 有对应的issue.

@aressu1985
Copy link
Contributor Author

testing

@ouyuanning
Copy link
Contributor

分支回归测试会有问题,还没时间处理

@ouyuanning
Copy link
Contributor

未投入

@ouyuanning
Copy link
Contributor

未投入

7 similar comments
@ouyuanning
Copy link
Contributor

未投入

@ouyuanning
Copy link
Contributor

未投入

@ouyuanning
Copy link
Contributor

未投入

@ouyuanning
Copy link
Contributor

未投入

@ouyuanning
Copy link
Contributor

未投入

@ouyuanning
Copy link
Contributor

未投入

@ouyuanning
Copy link
Contributor

未投入

@ouyuanning
Copy link
Contributor

先处理DML重构

1 similar comment
@ouyuanning
Copy link
Contributor

先处理DML重构

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working severity/s0 Extreme impact: Cause the application to break down and seriously affect the use
Projects
None yet
Development

No branches or pull requests

5 participants