A crash that leaves behind an InnoDB temporary table with temporary indexes results in an unbootable server
|Percona Server||Status tracked in 5.6|
No concrete test case yet, but it needs a temporary table that has at least one index and a server crash that leaves such table behind.
Subsequent server reboots will try to remove such table and fail:
120514 6:43:57 InnoDB: Assertion failure in thread 47327229830816 in file dict0dict.c line 868
InnoDB: Failing assertion: table2 == NULL
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: about forcing recovery.
- Alexey Kopytov (community): Approve on 2012-05-16
Diff: 80 lines (+43/-1)5 files modifiedPercona-Server/mysql-test/suite/innodb/r/percona_bug_999147.result (+10/-0)
- Alexey Kopytov (community): Approve on 2012-05-17
Diff: 80 lines (+43/-1)5 files modifiedPercona-Server/mysql-test/suite/innodb_plugin/r/percona_bug_999147.result (+10/-0)
A crash that leaves behind an InnoDB temporary table with indexes
- results in unbootable server
+ results in an unbootable server
|Laurynas Biveinis (laurynas-biveinis) wrote : Re: A crash that leaves behind an InnoDB temporary table with indexes results in an unbootable server||#1|
- A crash that leaves behind an InnoDB temporary table with indexes
- results in an unbootable server
+ A crash that leaves behind an InnoDB temporary table with temporary
+ indexes results in an unbootable server