Log tracking is incompatible with innodb_force_recovery=6

Bug #1083596 reported by Laurynas Biveinis
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Laurynas Biveinis
Fix Released
Laurynas Biveinis
Fix Released
Laurynas Biveinis

Bug Description

--innodb_track_changed_pages=TRUE --innodb_force_recovery=6:

InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
InnoDB: Error: last tracked LSN is in future. This can be caused by mismatched bitmap files.

And the server quits. The fix is to skip log tracking initialization on forced recovery.

Related branches

description: updated
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-1280

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

Other bug subscribers