Log tracking is initialized too late during InnoDB startup

Bug #1076892 reported by Laurynas Biveinis on 2012-11-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server
Laurynas Biveinis
Laurynas Biveinis
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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers