[MDEV-11455] shutdown or abort during innodb buffer pool load (from file) causing incomplete save Created: 2016-12-02 Updated: 2018-02-23 Resolved: 2018-02-23 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.0.6 |
| Fix Version/s: | 10.3.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Black | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | contribution, foundation | ||
| Description |
|
Assuming innodb_buffer_pool_load_at_startup is set (default from 10.2.2) and that a previous shutdown generated a viable dump file, and abort (innodb_buffer_pool_load_abort) or shutdown when this load is in progress will not result in an incomplete buffer pool. What is inconvenient is if this server is shutdown after limited activity the dump file (assuming innodb_buffer_pool_dump_at_shutdown is set) then the saved dump file will be significantly smaller (and suboptimal) compared to the original dump file. |
| Comments |
| Comment by Daniel Black [ 2016-12-02 ] |
|
pull request - proof of concept only so far - haven't done much testing on it. Feedback welcome. |
| Comment by Daniel Black [ 2016-12-06 ] |
|
test case added. Note: if accepted https://mariadb.com/kb/en/mariadb/status-variables-added-in-mariadb-102/ needs updating to include innodb_buffer_pool_load_incomplete |
| Comment by Daniel Black [ 2017-02-15 ] |
|
Approved by jplindst on github. Can this be merged? |
| Comment by Marko Mäkelä [ 2017-04-04 ] |
|
I am terribly sorry for the delay. It seems to me that the test may not be working as intended. |