mariadb/storage/innobase
unknown b352969118 MDEV-5914: Parallel replication deadlock due to InnoDB lock conflicts
Due to how gap locks work, two transactions could group commit together on the
master, but get lock conflicts and then deadlock due to different thread
scheduling order on slave.

For now, remove these deadlocks by running the parallel slave in READ
COMMITTED mode. And let InnoDB/XtraDB allow statement-based binlogging for the
parallel slave in READ COMMITTED.

We are also investigating a different solution long-term, which is based on
relaxing the gap locks only between the transactions running in parallel for
one slave, but not against possibly external transactions.
2014-03-21 13:30:55 +01:00
..
api InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
btr InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
buf MDEV-5574 Set AUTO_INCREMENT below max value of column. 2014-02-01 09:33:26 +01:00
data Fixing the bug 16919882 - WRONG FSF ADDRESS IN LICENSES HEADERS 2013-06-10 22:29:41 +02:00
dict InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
dyn MDEV-5574 Set AUTO_INCREMENT below max value of column. 2014-02-01 09:33:26 +01:00
eval Fixing the bug 16919882 - WRONG FSF ADDRESS IN LICENSES HEADERS 2013-06-10 22:29:41 +02:00
fil MDEV-5878: Failing assertion: mutex_own(mutex) with innodb_use_fallocate=ON. 2014-03-17 15:49:41 +02:00
fsp MDEV-5574 Set AUTO_INCREMENT below max value of column. 2014-02-01 09:33:26 +01:00
fts InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
fut Fixing the bug 16919882 - WRONG FSF ADDRESS IN LICENSES HEADERS 2013-06-10 22:29:41 +02:00
ha mysql-5.5.33 merge 2013-09-06 22:31:30 +02:00
handler MDEV-5914: Parallel replication deadlock due to InnoDB lock conflicts 2014-03-21 13:30:55 +01:00
ibuf InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
include MDEV-5878: Failing assertion: mutex_own(mutex) with innodb_use_fallocate=ON. 2014-03-17 15:49:41 +02:00
lock MDEV-5574 Set AUTO_INCREMENT below max value of column. 2014-02-01 09:33:26 +01:00
log InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
mach Fixing the bug 16919882 - WRONG FSF ADDRESS IN LICENSES HEADERS 2013-06-10 22:29:41 +02:00
mem MDEV-5574 Set AUTO_INCREMENT below max value of column. 2014-02-01 09:33:26 +01:00
mtr InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
mysql-test/storage_engine From MySQL 5.6.13 change log: 2014-02-05 16:41:29 +04:00
os MDEV-5878: Failing assertion: mutex_own(mutex) with innodb_use_fallocate=ON. 2014-03-17 15:49:41 +02:00
page MDEV-5574 Set AUTO_INCREMENT below max value of column. 2014-02-01 09:33:26 +01:00
pars null-merge from innodb-5.6 mergetree (as of 5.6.14) 2014-02-26 19:22:48 +01:00
que Fixing the bug 16919882 - WRONG FSF ADDRESS IN LICENSES HEADERS 2013-06-10 22:29:41 +02:00
read MDEV-5574 Set AUTO_INCREMENT below max value of column. 2014-02-01 09:33:26 +01:00
rem MDEV-5574 Set AUTO_INCREMENT below max value of column. 2014-02-01 09:33:26 +01:00
row InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
srv InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
sync InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
trx InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
usr Fixing the bug 16919882 - WRONG FSF ADDRESS IN LICENSES HEADERS 2013-06-10 22:29:41 +02:00
ut InnoDB 5.6.15 merge. 2014-02-26 19:36:33 +01:00
CMakeLists.txt workaround for xtradb on gcc 4.1.2 RHEL5/x86, gcc atomic ops only work under -march=i686 2014-03-07 17:47:47 +01:00
compile-innodb null-merge from innodb-5.6 mergetree (as of 5.6.14) 2014-02-26 19:22:48 +01:00
COPYING.Google Renamed storage/innodb_plugin to storage/innobase, so that 1) it's the same 2009-08-07 12:16:00 +02:00
COPYING.Percona Renamed storage/innodb_plugin to storage/innobase, so that 1) it's the same 2009-08-07 12:16:00 +02:00
Doxyfile Remove ut0auxconf.h. 2010-09-09 14:27:52 +03:00
ha_innodb.def Renamed storage/innodb_plugin to storage/innobase, so that 1) it's the same 2009-08-07 12:16:00 +02:00