Details
-
Bug
-
Status: Closed (View Workflow)
-
Trivial
-
Resolution: Fixed
-
10.3(EOL)
-
None
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.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue duplicates |
| Fix Version/s | 10.3.4 [ 22904 ] | |
| Fix Version/s | 10.3 [ 22126 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 82334 ] | MariaDB v4 [ 152734 ] |