Skip to content

seata1.4.2升级1.5.2后,报错Duplicate entry for key 'lock_table.PRIMARY' #4872

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.

Sign up for GitHub

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

Jump to bottom
Closed
elinebaba opened this issue Aug 17, 2022 · 1 comment · Fixed by #4681
Closed

seata1.4.2升级1.5.2后,报错Duplicate entry for key 'lock_table.PRIMARY' #4872

elinebaba opened this issue Aug 17, 2022 · 1 comment · Fixed by #4681

Comments

@elinebaba
Copy link

seata服务端1.5.2,客户端1.4.2,正常
seata服务端1.5.2,客户端1.5.2,服务端报错
Caused by: java.sql.SQLIntegrityConstraintViolationException: Duplicate entry 'jdbc:mysql://127.0.0.1:3306/financiallogic^^^logic_test_1^^^6827' for key 'lock_table.PRIMARY'
查看了下,数据源代理提交时,lock_table的row_key重复导致, 去掉主键约束发现row_key相同,xid相同,branch_id不相同
求解?
@funky-eyes
Copy link
Contributor

等后续修复版本，1.5做了insert不检查锁的功能导致delete后又insert场景不支持

@funky-eyes funky-eyes mentioned this issue Aug 18, 2022
Merged
1 task
@changeAtLater changeAtLater mentioned this issue Sep 6, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

optimize: lock priority attempts to insert funky-eyes/seata
2 participants
@funky-eyes @elinebaba