Not the answer you need?
Register and ask your own question!

Problems while upgrading Percona cluster from 5.6 to 5.7 due to innodb_log_block_size

ethanielethaniel EntrantInactive User Role Contributor
Hello everyone!

I have 3 servers running Percona 5.6 which are in a cluster.

I have innodb_log_block_size=4096 set on each one of them. The disks are SSD running ext4 filesystems formatted at 512 bytes. I chose innodb_log_block_size=4096 because several manuals mentioned that it's a better option for SSD disks.

I tried to perform a in-place upgrade from 5.6 to 5.7 (according to

It failed because innodb_log_block_size is set to 4096 (innodb_log_block_size was removed in 5.7):
[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

The manual ( states that I need to shutdown mysql, remove the variable from my.cnf configuration, remove the old logs and start the service again before doing the upgrade.

But since I'm running in a cluster, won't it cause problems during the upgrade? If I shutdown mysql, remove this option and remove the logs, won't the logs be syncronised back from other nodes once I start mysql back up?
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.