[MDEV-14909] MariaDB 10.2 refuses to start up after clean shutdown of MariaDB 10.3 Created: 2018-01-10  Updated: 2018-09-07  Resolved: 2018-01-10

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

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

Issue Links:
Blocks
blocks MDEV-13562 Documentation needed on downgrading f... Closed
Relates
relates to MDEV-17138 Reduce redo log volume for undo table... Closed

 Description   

MariaDB 10.3.2 changed the InnoDB redo log format tag.
By design, this causes older MariaDB versions to refuse downgrade on InnoDB files that had been modified with MariaDB 10.3.
We should allow MariaDB 10.2 to downgrade the 10.3 redo log if it is logically empty. We must keep refusing crash-downgrade, because 10.2 lacks the code to deal with some 10.3 redo log record types (and some undo log record types and B-tree format changes as well).

 Comments   
Comment by Marko Mäkelä [ 2018-01-10 ]

While implementing this, I also added a test for a successful upgrade from an earlier version to 10.2.

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