Task #13360

Investigate alternatives to the default transaction isolation level

Added by José Raddaoui Marín about 1 month ago. Updated about 1 month ago.

Status:NewStart date:06/15/2020
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Internals
Target version:-
Google Code Legacy ID: Tested version:2.6
Sponsored:No Requires documentation:

Description

We have been seeing DB deadlocks lately, in web requests (#12709) and CSV import (#13354) for example. We should analyze if using a different transaction isolation level could improve the situation.

Initial research:

- Designing Data-Intensive Applications (Chapter 7)
- https://dev.mysql.com/doc/refman/8.0/en/commit.html
- https://www.oreilly.com/library/view/mysql-reference-manual/0596002653/ch06s07.html
- https://mariadb.com/kb/en/set-transaction
- https://dev.mysql.com/doc/refman/8.0/en/innodb-locks-set.html
- https://dev.mysql.com/doc/refman/8.0/en/innodb-autocommit-commit-rollback.html

My initial impression is that to avoid the deadlock we could introduce lost updates and that we shouldn't change the current isolation level.

History

#1 Updated by José Raddaoui Marín about 1 month ago

  • Description updated (diff)

Also available in: Atom PDF