Log tracking is initialized too late during InnoDB startup

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

Bug Description

Currently innobase_start_or_create_for_mysql() initializes log tracking subsystem late, after crash recovery has been run. It should be moved to right after reading the checkpoint info from the logs instead. The late initialization introduces some non-determinism in what bitmap files will be created with what starting LSNs due to crash recovery running in background.

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-1278

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.