Attempt fixing deadlocks by moving account stats update outside transaction #9437
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.
increment_counter_caches
may cause deadlocks when multiple jobs touch the same account.From my understanding, this is because
Status.create
is always called inside a transaction, andincrement_counter_caches
will be called within that transaction, causing both a read and a write of that particular row within the same transaction.This PR makes the callback executes after the transaction.