[MDEV-11840] InnoDB: "Cannot open <ib_buffer_pool file>" should not be an error Created: 2017-01-19  Updated: 2017-04-06  Resolved: 2017-04-05

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2
Fix Version/s: 10.2.6

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: 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.



 Comments   
Comment by Marko Mäkelä [ 2017-04-04 ]

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

Generated at Thu Feb 08 07:53:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.