Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
As noted by knielsen, the group commit + SBR + release_locks_early test suffers sporadic failures. I was able to repeat against the latest mysql-5.3.
All the failures seem to have the following in common:
- the diff reports that the master has 2 or more rows more than the slave;
- the divering tables are always the ones that have no PK
Logs will be attached shortly.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
.result file for mysql-test-run test case
LPexportBug798213_innodb_release_locks_early_recovery.result
Re: --innodb-release-locks-early=1 breaks InnoDB crash recovery
Re: --innodb-release-locks-early=1 breaks InnoDB crash recovery
The attached test case (3 files in total) fails as follows in current MariaDB 5.3:
main.innodb_release_locks_early_recovery [ fail ]
Test ended at 2011-06-22 10:26:18
CURRENT_TEST: main.innodb_release_locks_early_recovery
— /home/knielsen/my/5.3/mariadb-5.3/mysql-test/r/innodb_release_locks_early_recovery.result 2011-06-22 10:26:00.000000000 +0200
+++ /home/knielsen/my/5.3/mariadb-5.3/mysql-test/r/innodb_release_locks_early_recovery.reject 2011-06-22 10:26:18.000000000 +0200
@@ -58,7 +58,7 @@
Got one of the listed errors
SELECT * FROM t1;
a b
-1 Base0
+1 Update c4
SELECT * FROM t2 ORDER by a;
a
DROP TABLE t1;
mysqltest: Result length mismatch
As explained above, we see here transaction c4 visible in table t1, even though it should have been rolled back (and is rolled back in table t2).
Re: --innodb-release-locks-early=1 breaks InnoDB crash recovery
The --innodb-release-locks-early feature has been removed from MariaDB 5.3 because of a fundamental issue with InnoDB crash replication.
Launchpad bug id: 798213
Datadir and logs. The rqg log is in rqg.log.failing. The files for the cloned slave are in clonedslave . The files in slave-data are from a normal slave that is not affected by xtrabackup+restore.
var-bug798213.zip
LPexportBug798213_var-bug798213.zip