Geek Answers Handbook

Mysql XA isolation level

Does anyone know why Mysql requires a serializable isolation level to achieve ACID properties with XA transactions, or what will be lost if you use repeatable reading and XA?

However, for a distributed transaction, you must use the SERIALIZABLE isolation level before you reach ACID properties. It is enough to use REPEATABLE READ for an unallocated transaction, but not for a distributed transaction.

http://dev.mysql.com/doc/refman/5.6/en/xa.html

+4
source share
1 answer

I believe this is due to the nature of REPEATABLE READ and the XA restrictions in the mysql engine (MySQL does not fully comply with the XA specification).

A known issue is that some replication failure scenarios may result in a missing transaction from binlog: From: XA transaction restrictions

With the above, Consistency in ACID is lost.

I assume that strict behavior caused by SERIALIZABLE reduces this to the extent necessary for how they describe xid operation, etc. But the development of these issues is suspiciously missing. Mysql 5.6 - Consistent Reading

+1
source

More articles:


All Articles