[MDEV-14848] MariaDB 10.3 refuses InnoDB crash-upgrade from MariaDB 10.2 Created: 2018-01-01  Updated: 2018-04-26  Resolved: 2018-01-04

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.3.2, 10.3.3
Fix Version/s: 10.3.4

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: backup, recovery, upgrade

Issue Links:
Duplicate
is duplicated by MDEV-13688 Error messages upon refusal to crash-... Closed
Relates
relates to MDEV-11369 Instant add column for InnoDB Closed
relates to MDEV-12288 Reset DB_TRX_ID when the history is r... Closed

 Description   

While the redo log format was changed in MariaDB 10.3.2 and 10.3.3 due to MDEV-12288 and MDEV-11369, it should be technically possible to upgrade from a crashed MariaDB 10.2 instance.

On a related note, it should be possible for Mariabackup 10.3 to create a backup from a running MariaDB Server 10.2.

Currently, both these are refused due to redo log format tag mismatch. We should remove the refusal and test the upgrade.

The format tag will still serve its main purpose: preventing an older version of MariaDB from starting up from newer InnoDB files. Even that one we could theoretically relax if desired, in a separate issue: allow 10.2 to start up on files left behind by a clean shutdown of 10.3.


Generated at Thu Feb 08 08:16:45 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.