Assertion failure on --prepare --apply-log-only
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Alexey Kopytov | ||
1.6 |
Fix Released
|
High
|
Alexey Kopytov | ||
2.0 |
Fix Released
|
High
|
Alexey Kopytov |
Bug Description
In MySQL 5.1.57 a new assertion was added as a part of the fix for http://
xtrabackup: starting shutdown with innodb_
120221 8:35:01 InnoDB: Starting shutdown...
120221 8:35:01 InnoDB: Assertion failure in thread 46955612838640 in
file trx/trx0sys.c line 1914
InnoDB: Failing assertion: UT_LIST_
trx_n_prepared
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
Aborted
Since the assertion was introduced in 5.1.57 and XtraBackup was rebased from 5.1.55 to 5.1.59 in version 1.6.4, it's a regression from 1.6.3.
Related branches
- Stewart Smith (community): Approve
-
Diff: 82 lines (+48/-3)3 files modifiedpatches/innodb55.patch (+16/-1)
patches/xtradb51.patch (+16/-1)
patches/xtradb55.patch (+16/-1)
- Stewart Smith (community): Approve
-
Diff: 110 lines (+64/-4)4 files modifiedpatches/innodb51.patch (+16/-1)
patches/innodb55.patch (+16/-1)
patches/xtradb51.patch (+16/-1)
patches/xtradb55.patch (+16/-1)
summary: |
Assertion failure on --prepare --apply-log-only when XA transactions are + used |
summary: |
- Assertion failure on --prepare --apply-log-only when XA transactions are - used + Assertion failure on --prepare --apply-log-only |
I've tested this branch and it fixes the problem we were having too. It wasn't from a XA transaction, but we were getting the same assertion failure.
Also, our prepare times for --redo-only have gone from about 30 minutes to 15 seconds, (doesn't seem to do log recovery at all anymore) not sure if it should've been like this before but the tested backups are still valid so that's pretty good!