Re: mysql crash InnoDB: MySQL is trying to perform a consistent read but the read view is not assigned!

[Richard Lee]

We have made some findings which might be helpful if anyone else has the same issue.

Whilst we don't yet know what exactly is causing the issue, we do seem to have narrowed it down to tables using the MEMORY engine. We were able to reliably cause the server to crash by issuing the following command against the affected tables: "SHOW INDEXES FROM [schema].[table]"

This would cause an InnoDB assertion error at row0sel.cc, line 4630.


We were able to "repair" the tables by swapping them to the MyISAM engine and then back to MEMORY. After this the same query works fine reliably.


We then tried to cause the fault to occur again afterwards, but have not since been able to replicate, e.g. by following exactly the same deployment process as those tables had originally, which was through loading a mysqldump result from version 5.5.12 (using the mysqldump executable from that version).