Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Fix deadlocks and races when making form variables state consistent #5064
Fix deadlocks and races when making form variables state consistent #5064
Changes from all commits
9c61599
3eac8ed
3eb1fd2
d86a1bb
d1fdb80
36e0a90
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For my understanding: did the deadlock issue occur when two admins were modifying two different forms that shared a reusable form definition? Is this fixed now because it no longer does the recoupling via celery?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the problem was that the task was scheduled to run 60s later and other write actions were happening and multiple transactions were trying to lock the same records in the table and competing for resources. Celery is definitely a big factor in this issue.
Laurens also saw issues when saving different forms in the admin in different tabs, so you didn't even need multiple different users doing stuff at the same time, but one customer was apparently building forms with 4 different people so that will have manifested much more obviously.