Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.2(EOL)
-
None
Description
In InnoDB 5.7 innodb_buffer_pool_load_at_startup has become ON by default. Now InnoDB produces an error when it starts and doesn't find the dump of the buffer pool.
2017-01-19 13:51:49 140427969689344 [ERROR] InnoDB: Cannot open '/data/bld/10.2/data/ib_buffer_pool' for reading: No such file or directory
|
It can happen, for example, on upgrade from a previous version.
But in fact the situation is harmless, so it shouldn't be an error – a warning, at most.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | InnoDB: "Cannot open <ib_buffer_pool>" should be a warning, not an error | InnoDB: "Cannot open <ib_buffer_pool file>" should be a warning, not an error |
| Summary | InnoDB: "Cannot open <ib_buffer_pool file>" should be a warning, not an error | InnoDB: "Cannot open <ib_buffer_pool file>" should not be an error |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Fix Version/s | 10.2.5 [ 22117 ] | |
| Fix Version/s | 10.2 [ 14601 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Fix Version/s | 10.2.6 [ 22527 ] | |
| Fix Version/s | 10.2.5 [ 22117 ] |
| Workflow | MariaDB v3 [ 79276 ] | MariaDB v4 [ 151559 ] |
The buffer pool dump/load messages are reported via a wrapper function that uses only two values, mapping to NOTE and ERROR. I agree that inability to open a dump file for reading should not be reported as an error. Because we cannot easily report warnings, I’d make it a note.
http://lists.askmonty.org/pipermail/commits/2017-April/010974.html