Problem/Motivation

By default, Drupal uses the "REPEATABLE READ" transaction isolation level - this results in lots of deadlock errors.

Serialization failure: 1213 Deadlock found when trying to get lock

The issue Use READ COMMITTED by default for MySQL transactions sets the isolation level only if it is explicitly configured in settings.php.

All high-traffic sites need to use the "READ COMMITTED" transaction isolation level without any requirements in settings.php.

Issue fork drupal-3336720

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

martin_klima created an issue. See original summary.

martin_klima opened merge request !3298

cilefen’s picture

cilefen commented

This seems like an argument to make on the #1650930: Use READ COMMITTED by default for MySQL transactions issue rather than a separate bug report.

martin_klima’s picture

martin_klima
he/his
Primary language Czech
commented

I've been thinking about it. Since the development of issue 1650930 is moving towards a comprehensive solution including configuration, I thought it would be better to offer this simpler alternative approach in a separate issue.

martin_klima opened merge request !3302

daffie’s picture

daffie commented
Status: Active » Closed (won't fix)

This has been fixed in #1650930: Use READ COMMITTED by default for MySQL transactions.
This will not be backported to D10.0 or D9.5.