Bug #76656 Please don't save the buffer pool if it's almost empty
| Submitted: | 10 Apr 2015 11:04 | Modified: | 17 Aug 2015 16:44 |
|---|---|---|---|
| Reporter: | Simon Mudd | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S4 (Feature request) |
| Version: | 5.6/5.7 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | buffer_pool, innodb, upgrade | ||
[10 Apr 2015 11:04]
Simon Mudd
[10 Apr 2015 11:44]
Simon Mudd
If you do this please adjust the logging: Currently it says: 2015-04-10T10:34:12.475906Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 150410 12:34:12 2015-04-10T10:35:02.481751Z 0 [Note] InnoDB: Buffer pool(s) load completed at 150410 12:35:02 Add the size of the buffer pool that's been saved. Pages will do but maybe provide an equivalent value in MB/GB as that's easier to understand. The 2nd timestamp is superfluous so remove it (and show how long it took). Something along the lines of: 2015-04-10T10:34:12.475906Z 0 [Note] InnoDB: Buffer pool(s) dump of XXX pages (YYY MB) completed in 9.999 seconds # this will be fast 2015-04-10T10:35:02.481751Z 0 [Note] InnoDB: Buffer pool(s) load of XXX pages (YYY MB) completed in 999.9 seconds # this will obviously take longer
[13 Apr 2015 6:23]
Shane Bester
As a workaround can one set innodb_buffer_pool_dump_pct=100 before the second restart to avoid reducing the existing 25% to 6.25%?
[17 Aug 2015 16:41]
Simon Mudd
See also: bugs#68863
[17 Aug 2015 16:44]
Simon Mudd
Sorry, See also: bug#68863
[3 Jun 2019 11:38]
Shane Bester
see also FR https://bugs.mysql.com/bug.php?id=95603
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.059 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.