Server won't start with innodb_force_recovery=6 because parallel doublewrite file exists

Bug #1629879 reported by Tomislav Plavcic
6
This bug affects 1 person
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_force_recovery=6 the server won't start because the parallel doublewrite file exists so you get something like:
2016-10-03T13:15:06.447344Z 0 [ERROR] InnoDB: A parallel doublewrite file /ssd/tomislav/Percona-Server-5.7.14-7-Linux.x86_64.ssl101/data/xb_doublewrite found on startup.
2016-10-03T13:15:06.447355Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2016-10-03T13:15:07.448574Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2016-10-03T13:15:07.448611Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-10-03T13:15:07.448619Z 0 [ERROR] Failed to initialize plugins.
2016-10-03T13:15:07.448627Z 0 [ERROR] Aborting

TEST CASE:
Sysbench prepare:
sysbench --test=/usr/share/doc/sysbench/tests/db/oltp.lua --report-interval=1 --oltp-tables-count=1 --oltp-table-size=1000 --max-time=0 --oltp-read-only=off --max-requests=0 --num-threads=64 --rand-type=pareto --db-driver=mysql--mysql-db=sbtest --mysql-user=root prepare

Sysbench run:
sysbench --test=/usr/share/doc/sysbench/tests/db/oltp.lua --report-interval=1 --oltp-tables-count=1 --oltp-table-size=1000 --max-time=0 --oltp-read-only=off --max-requests=0 --num-threads=64 --rand-type=pareto --db-driver=mysql--mysql-db=sbtest --mysql-user=root run

During the sysbench run kill the server with -9 and try to start the server with --innodb_force_recovery=6.

This was noticed while checking https://bugs.launchpad.net/percona-server/+bug/1629250 where Oracle MySQL can be started with innodb_force_recovery=6 but PS won't start even with that value.

tags: added: parallel-doublewrite regression xtradb
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

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)

tags: removed: regression
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1752

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.