Option to block start InnoDB until LRU is preloaded from dump
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Wishlist
|
Alexey Kopytov | |
| 5.1 |
Fix Released
|
Wishlist
|
Alexey Kopytov | |
| 5.5 |
Fix Released
|
Wishlist
|
Alexey Kopytov | |
| codership-maria |
Undecided
|
Unassigned |
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-
Related branches
- Stewart Smith (community): Approve on 2011-09-26
-
Diff: 203 lines (+65/-12)2 files modifiedpatches/innodb_lru_dump_restore.patch (+63/-12)
patches/mysql-test.diff (+2/-0)
- Stewart Smith (community): Approve on 2011-09-27
-
Diff: 227 lines (+77/-13)2 files modifiedpatches/innodb_lru_dump_restore.patch (+73/-11)
patches/mysql-test.diff (+4/-2)
tags: | added: galera |
Stewart Smith (stewart) wrote : | #1 |
Alexey Kopytov (akopytov) wrote : | #2 |
Assuming this is targeted for 5.1.59-13.0 too.
Alexey Kopytov (akopytov) wrote : | #3 |
Quoting revision comments for 5.1:
"
Bug #785489: Option to block start InnoDB until LRU is preloaded from
dump
Added a new boolean option, --innodb-
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-
Shahriyar Rzayev (rzayev-sehriyar) wrote : | #4 |
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/
Vadim, or should I assign to you? :)