Percona Server moved to https://jira.percona.com/projects/PS

Add 5.6 non-default innodb_log_block_size setting detection to 5.7

  1. Series 5.7
  2. Bug #1647997
Bug #1647997 reported by Laurynas Biveinis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.5
Invalid
Undecided
Unassigned
5.6
Invalid
Undecided
Unassigned
5.7
Triaged
Medium
Unassigned

Bug Description

Split from bug 1647728.

Currently, if an in-place 5.6 to 5.7 upgrade is attempted with 5.6 logs created with non-default innodb_log_block_size setting, the resulting error message is not very helpful:

2016-12-06T13:39:36.190839Z 0 [ERROR] InnoDB: Upgrade after a crash is not supported. This redo log was created before MySQL 5.7.9, and we did not find a valid checkpoint. Please follow the instructions at http://dev.mysql.com/doc/refman
/5.7/en/upgrading.html

A better error should be shown instead.

Tags: xtradb
Laurynas Biveinis (laurynas-biveinis)
tags: added: xtradb
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1767

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.