[MDEV-13688] Error messages upon refusal to crash-upgrade can be misleading Created: 2017-08-31  Updated: 2018-01-15  Resolved: 2018-01-15

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

Type: Bug Priority: Trivial
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-14848 MariaDB 10.3 refuses InnoDB crash-upg... Closed

 Description   

When current 10.3 server attempts to crash-upgrade from current 10.1, e.g. 10.1.26, it says

10.3 e1051590b61b455

2017-08-31  4:13:38 0 [ERROR] InnoDB: Upgrade after a crash is not supported. This redo log was created before MariaDB 10.2.2.
2017-08-31  4:13:38 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[2218] with error Generic error

which kind of implies that if redo log was created after 10.2.2, it would have been supported.

However, upon crash-upgrade from the current 10.2 (e.g. 10.2.8) it says

10.3 e1051590b61b455

2017-08-31  2:37:53 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.2.8.
2017-08-31  2:37:53 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[2218] with error Generic error

It's not critical, but maybe some clean-up is due there.



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

After MDEV-14848, MariaDB 10.3 will allow a crash-upgrade from MariaDB 10.2.

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