[MDEV-12700] Allow innodb_read_only startup without prior slow shutdown - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Won't Do
Affects Version/s: 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL)
Fix Version/s: 11.0.1
Component/s: Storage Engine - InnoDB
Labels:

Description

The parameter innodb_read_only which first appeared in MySQL 5.6 and MariaDB Server 10.0 disallows startup if the redo log is not logically empty or if the change buffer is not empty.

It is technically possible to apply the needed changes in memory only, without writing them back to the data files. If MariaDB does that, it will be possible to check hot backups in a read-only fashion without any preparatory steps.

Attachments

Issue Links

includes

MDEV-19514 Defer change buffer merge until pages are requested

Closed

is blocked by

MDEV-14481 Execute InnoDB crash recovery in the background

Closed

is duplicated by

MDEV-13614 Allow --innodb-read-only startup even when change buffer or redo logs are not empty

Closed

relates to

MDEV-19176 Do not run out of InnoDB buffer pool during recovery

Closed

MDEV-11814 Refuse innodb_read_only startup if crash recovery is needed

Closed

MDEV-12699 Improve crash recovery of corrupted data pages

Closed

MDEV-14080 InnoDB shutdown sometimes hangs

Closed

MDEV-15202 innodb.log_file_size failed in buildbot - Can't initiate database recovery, running in read-only-mode

Closed

MDEV-29694 Remove the InnoDB change buffer

Closed

(4 relates to)

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 1 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2017-05-05 08:03

Updated:: 2023-06-07 07:13

Resolved:: 2023-06-07 07:13

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.