Server won't start with innodb_force_recovery=6 because parallel doublewrite file exists
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Invalid
|
Undecided
|
Unassigned | |||
5.7 |
Fix Released
|
Medium
|
Laurynas Biveinis |
Bug Description
If the server crashes and you need to use --innodb_
2016-10-
2016-10-
2016-10-
2016-10-
2016-10-
2016-10-
TEST CASE:
Sysbench prepare:
sysbench --test=
Sysbench run:
sysbench --test=
During the sysbench run kill the server with -9 and try to start the server with --innodb_
This was noticed while checking https:/
tags: | added: parallel-doublewrite regression xtradb |
We are actually more safe than the upstream here: http:// bugs.mysql. com/bug. php?id= 83255.
Keeping the bug open to improve diagnostics (suggest to move xb_doublewrite away for force recovery, and move it back for the restart with the redo log application)