enterprise-support team mailing list archive

Thread
Date

[Bug 1719284] Re: InnoDB error after 5.5 - 5.6 upgrade on Slave

To: enterprise-support@xxxxxxxxxxxxxxxxxxx
From: Nickolay Ihalainen <ihanick@xxxxxxxxx>
Date: Wed, 04 Oct 2017 12:57:18 -0000
Reply-to: Bug 1719284 <1719284@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Hi Michael,

The problem caused by incorrect upgrade procedure.

In place upgrade to mysql 5.6 or 5.7 require shutdown with
innodb_fast_shutdown=0 before upgrading packages.

For current state: install 5.5 binaries, start mysqld with skip-slave-
start, prevent external connections from application, execute
innodb_fast_shutdown=0, shutdown mysqld.

For details you can look inside: https://bugs.mysql.com/bug.php?id=69274

** Changed in: percona-server/5.6
       Status: Confirmed => Invalid

** Changed in: percona-server/5.7
       Status: Confirmed => Invalid

** Bug watch added: MySQL Bug System #69274
   http://bugs.mysql.com/bug.php?id=69274

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1719284

Title:
  InnoDB error after 5.5 - 5.6 upgrade on Slave

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1719284/+subscriptions