[MDEV-30819] InnoDB fails to start up after downgrading from MariaDB 11.0 - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.11.1, 10.5.19, 10.6.12, 10.7.8, 10.8.7, 10.9.5, 10.10.3
Fix Version/s: 10.11.3, 10.5.20, 10.6.13, 10.8.8, 10.9.6, 10.10.4
Component/s: Storage Engine - InnoDB
Labels:
None

Description

Downgrades are not supported, and in fact, a downgrade from MariaDB Server 10.8 or later to earlier versions is nontrivial due to ~~MDEV-27199~~ and ~~MDEV-14425~~.

The error message that was added in ~~MDEV-30106~~ may be confusing, and in fact, we can safely allow a downgrade, provided that the change buffering is never enabled.

2023-03-09 13:54:30 0 [ERROR] InnoDB: The change buffer is corrupted

2023-03-09 13:54:30 0 [ERROR] InnoDB: Plugin initialization aborted with error

Data structure corruption

2023-03-09 13:54:30 0 [Note] InnoDB: Starting shutdown...

If innodb_change_buffering=none (the default since ~~MDEV-27734~~), we can demote this error to a warning and allow InnoDB to start up.

Attachments

Issue Links

is caused by

MDEV-30106 InnoDB fails to validate the change buffer on startup

Closed

relates to

MDEV-27734 Set innodb_change_buffering=none by default

Closed

MDEV-29694 Remove the InnoDB change buffer

Closed

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2023-03-09 12:56

Updated:: 2023-03-09 14:53

Resolved:: 2023-03-09 14:53

Git Integration

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