Support InnoDB buffer pool dumps in MySQL 5.6

Registered by Alexey Kopytov on 2012-11-23

InnoDB in MySQL 5.6 has the buffer pool preload feature similar to LRU dump/restore in Percona Server. There's also a number of new innodb_buffer_pool_* system variables, controlling the behavior (incl. the name of the dump file, see innodb_buffer_pool_filename).

This BP is to implement support for 5.6-style buffer pool dumps in addition to ib_lru_dump file in Percona Server 5.1/5.5.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
Alexey Kopytov
Direction:
Needs approval
Assignee:
Sergei Glushchenko
Definition:
Approved
Series goal:
Accepted for 2.1
Implementation:
Implemented
Milestone target:
None
Started by
Alexey Kopytov on 2013-04-27
Completed by
Alexey Kopytov on 2013-04-29

Whiteboard

   Starting with MySQL 5.6 one can produce buffer pool dumps and load them for faster
   server warmup after the start. This feature is similar to LRU dump in XtraDB.
   This blueprint adds support for buffer pool dumps into Xtrabackup. Dump is
   copied into backup directory during the backup stage.
   During the copy back stage (restore) it copied back to data directory.
   After restore dump can be loaded by the server either automatically on
   startup or on demand.
   MySQL 5.6 feature http://dev.mysql.com/doc/refman/5.6/en/innodb-performance.html#innodb-preload-buffer-pool.
   Similar XtraDB feature http://www.percona.com/doc/percona-server/5.5/management/innodb_lru_dump_restore.html.
   XtraBackup feature http://www.percona.com/doc/percona-xtrabackup/xtrabackup_bin/lru_dump.html.
   Xtrabackup will copy buffer pool dump if it name is specified by innodb_buffer_pool_filename
   option in my.cnf. If value has been set dynamically it will not be seen by Xtrabackup.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.