-
Type:
Bug
-
Status: Done
-
Priority:
Medium
-
Resolution: Fixed
-
Affects Version/s: 5.7.27-30, Not 8.0.x
-
Fix Version/s: 5.7.31-34
-
Component/s: None
-
Labels:None
While running pstress, mysql server failed to perform crash recovery. After the server was crashed, it fails to recover. As per error logs:
InnoDB: Tablespace 192 was not found at /tmp/719168/3/tmp/#sql1a4b_10_5.ibd.
InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace.
InnoDB: Cannot continue operation.
Options to reproduce the problem:
--tables 20 --records 700 --only-temp-tables --no-select --no-insert --no-delete --no-update --log-all-queries --log-failed-queries
This issue is a regression introduced in 5.7.27-30 by this commit id 079693537f0 as part of
PS-5736 - Make innodb_temp_tablespace_encrypt truly dynamic
The error message in the logs are quite relatable as well.
InnoDB: Tablespace 192 was not found at /tmp/719168/3/tmp/#sql1a4b_10_5.ibd.
Steps to verify that this a regression:
git checkout release-5.7.30-33
git revert 079693537f0 -m 1
Run pstress. Issue will not be seen
- is caused by
-
PS-6788 Merge MySQL 5.7.30
-
- Done
-