Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.6, 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.4, 11.5(EOL)
-
None
Description
Crash recovery tests with concurrent FK operations on non-debug builds trigger the error upon crash recovery:
|
10.6 5ba542e9eec0ef5d69883c89755211f7d0e5d0e1 |
2024-05-31 0:15:55 0 [Note] Plugin 'FEEDBACK' is disabled.
|
2024-05-31 0:15:55 0 [ERROR] DDL_LOG: Got error 1050 when trying to execute action for entry 4 of type 'alter table'
|
2024-05-31 0:15:55 0 [Note] DDL_LOG: Crash recovery executed 2 entries
|
2024-05-31 0:15:55 0 [Note] Server socket created on IP: '0.0.0.0'.
|
rr profiles of both sessions before and during crash recovery are provided.
In the original tests the assertion failure
InnoDB: Failing assertion: table2 == NULL
|
was also seen.
Notes on reproducing:
The DDL error is reproducible for me reasonably well on non-debug builds with the concurrent test below. The InnoDB failure however doesn't seem to be happening with this test.
git clone https://github.com/MariaDB/randgen mdev34252 rqg-mdev34252
|
cd rqg-mdev34252
|
. ./mdev34252.cmd <basedir> [--trials=10]
|
--trials is optional, by default the command line contains trials=5, but it can be increased if the failure isn't happening.
I haven't seen it on debug builds, maybe the timing is different, or possibly the tests fail in a different way.