Option to block start InnoDB until LRU is preloaded from dump

Bug #785489 reported by Vadim Tkachenko on 2011-05-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov

Bug Description

It may be not obvious why it is needed, but it is for integration Percona Server with Galera replication.
When we propagate new node we want node to start in "warm" state, and for this - preload buffer pool dump from disk before
InnoDB reports to MySQL that it started.

Looking into source code - it is just two-lines fix.

I propose to make special startup option i.e. --enable-blocking-lru-preload or like that which will trigger this behavior

Related branches

tags: added: galera
Stewart Smith (stewart) wrote :

Vadim, or should I assign to you? :)

Alexey Kopytov (akopytov) wrote :

Assuming this is targeted for 5.1.59-13.0 too.

Alexey Kopytov (akopytov) wrote :

Quoting revision comments for 5.1:

      Bug #785489: Option to block start InnoDB until LRU is preloaded from

      Added a new boolean option, --innodb-blocking-lru-restore, which is OFF
      by default. When set to ON, restoring from the LRU dump file is
      synchronous, i.e. InnoDB waits until it is complete before reporting
      successful startup to the server.

In 5.5, the option name is innodb-blocking-buffer-pool-restore (to be consistent with innodb-buffer-pool-restore-at-startup).

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

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

Other bug subscribers