[MDEV-13614] Allow --innodb-read-only startup even when change buffer or redo logs are not empty Created: 2017-08-22  Updated: 2017-11-30  Resolved: 2017-11-30

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.0
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Duplicate Votes: 0
Labels: recovery, startup

Issue Links:
Duplicate
duplicates MDEV-12700 Allow innodb_read_only startup withou... Closed
Relates
relates to MDEV-13485 MTR tests fail massively with --innod... Closed

 Description   

InnoDB refuses read-only startup when the redo log or the change buffer are not empty, issuing the following kind of messages:

[Warning] InnoDB: innodb_read_only prevents crash recovery
 
[ERROR] InnoDB: Change buffer must be empty when --innodb-read-only is set!

We should remove this arbitrary restriction in MariaDB Server.
It would be entirely possible to apply such changes in the buffer pool, only disabling the writes back to the data files in --innodb-read-only mode.
Generated at Thu Feb 08 08:06:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.