-
-
Notifications
You must be signed in to change notification settings - Fork 864
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
Allow transaction-isolation
level to be configured
#380
Comments
transaction-isolation
to READ-COMMITTED
by defaulttransaction-isolation
to READ-COMMITTED
by default (Serialization failure: 1213 Deadlock)
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! Please read this blog post to see the reasons why I mark issues as stale. |
This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details. |
This should at least be configurable. See Drupal's docs on it: Setting the MySQL transaction isolation level |
transaction-isolation
to READ-COMMITTED
by default (Serialization failure: 1213 Deadlock)transaction-isolation
level to be configured
https://www.drupal.org/project/drupal/issues/2833539#comment-12500749
Would like to discuss setting
transaction-isolation
toREAD-COMMITTED
by default as it solves a random, inconsistent flicker "SQLSTATE[40001]: Serialization failure: 1213 Deadlock" in some cases.The default is currently:
The text was updated successfully, but these errors were encountered: