[MDEV-19136] mysql_upgrade from mysql 5.7 to MariaDB 10.3.12 fails Created: 2019-04-02  Updated: 2021-05-24  Resolved: 2021-05-24

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.3.12
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Faisal Saeed (Inactive) Assignee: Marko Mäkelä
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

CentOS 7.4

Issue Links:
Relates
relates to MDEV-12289 Keep 128 persistent rollback segments... Closed

 Description   

Upgrading MySQL 5.7 to MariaDB 10.3.12 completes but gives the following error messages upon server restart.

"2019-02-12 14:49:39 0 [ERROR] InnoDB: Page [page id: space=76, page number=813] log sequence number 42628278 is in the future! Current system log sequence number 2433657.

2019-02-12 14:49:39 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery."

Process:
1. remove MySQL binaries (rpm -qa | grep mysql | xargs rpm -e)
2. Install MariaDB (yum -y install MariaDB-server)
3. mysql_upgrade

 Comments   
Comment by Elena Stepanova [ 2019-04-02 ]

We have quite a few reports with this error, not even necessarily upgrade. I can't tell if all of them have the same root cause or not, leaving it to marko to decide.

Comment by Marko Mäkelä [ 2021-04-26 ]

A known source of incompatibility between MySQL 5.7 and MariaDB 10.2 or later MDEV-12289. MariaDB retained 128 rollback segments in the TRX_SYS header.

MariaDB Server 10.3 introduced more undo log format changes (MDEV-12288, MDEV-15158), but they should have been compatible with older versions. The only caveat is that the server must be shut down cleanly before upgrading to MariaDB Server 10.3 or later in order to avoid MDEV-15912.

The message in the description does not match these symptoms, unless innodb_undo_tablespaces resides between 76 and 128.

I would need a complete test case (starting from installing the MYSQL 5.7 server and loading the database with some data) in order to be able to diagnose this.

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