[MDEV-9904] InnoDB 5.7 redo log in 10.0 Created: 2016-04-12 Updated: 2017-05-18 Resolved: 2016-04-15 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Platform Debian, Storage Engine - InnoDB, Storage Engine - XtraDB |
| Affects Version/s: | 10.0, 10.1 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Critical |
| Reporter: | Sergei Golubchik | Assignee: | Sergei Golubchik |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Ubuntu got MySQL 5.7. MariaDB 10.0 (that uses InnoDB 5.6) cannot be installed on top of that, because InnoDB 5.6 does not understand redo logs of 5.7. |
| Comments |
| Comment by Sergei Golubchik [ 2016-04-12 ] |
|
One option would be to delete 5.7 redo logs. This is only safe to do if InnoDB 5.7 was shut down cleanly. Another idea is to teach 10.0 to skip the version record in 5.7 logs. This works if the version is the only difference between 5.6 and 5.7 redo logs. |
| Comment by Sergei Golubchik [ 2016-04-15 ] |
|
There are too many changes in 5.7 that make downgrade quite difficult. We cannot account for them all in 10.0 and fixing only this one InnoDB redo log issue won't help much. |
| Comment by Otto Kekäläinen [ 2016-04-16 ] |
|
For the record, I solved this scenario by renaming the datadir to mysql-5.7 so users can proceed with dpkg and then manually recover (if there is anything to recover, most of the time I guess people are just testing with installs in development environments). https://github.com/ottok/mariadb-10.0/commit/9605a48a99a61f439698676da192799de45d732a |