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?
to your account
MyeongHyeonLee opened DATAJDBC-488 and commented
Deadlock occurs when UPDATE races with the same ID of an AggregateRoot with an association.
When UPDATE is executed, the WritingContext executes in the following order.
If many requests occur at the same time, a deadlock occurs between the Root and Referenced tables.
Deadlock occurs in the test case below.
Affects: 2.0 M3 (Neumann)
Reference URL: https://github.com/spring-projects/spring-data-jdbc/pull/191/files#diff-96c4ebdaa99aec19171b092995e4e765R70
Referenced from: pull request #191
Backported to: 1.1.5 (Moore SR5)
The text was updated successfully, but these errors were encountered:
Mark Paluch commented
Care to elaborate on how changing the order of execution fixes the issue? Right now it appeals that the root would hold the lock instead of assuming the DELETE would lock the reference tables
Sorry, something went wrong.
Deadlock can occur when there is no data in reference table.
Thanks a lot for the detail. That makes a lot of sense. Just waiting for Jens Schauder to approve that we haven't overseen anything that might interfere here
Jens Schauder commented
That's a good catch. Thanks for the great work
No branches or pull requests