my_myql: Handle deadlocks in mysql_stmt_execute #162
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We've seen deadlocks when mxqkill races with job completion. Handle deadlocks errors in mysql_stmt_execute. This is possible, because we don't start multi-statement transactions.
|
mxqd with this fix installed (without release or bee) on distmaster, pushed to cluster nodes and re-execed all mxqd daemons. This is experimental. |
|
Included in 0.31.6 |
Sign in
to join this conversation on GitHub.
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.
We've seen deadlocks when mxqkill races with job completion.
Handle deadlocks errors in mysql_stmt_execute. This is possible, because we don't start multi-statement transactions.
Experimental fix for #161