Slave replication fails on master upgrade 'InnoDB does not support system tables'
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Fix Released
|
High
|
Laurynas Biveinis | |||
5.6 |
Fix Released
|
High
|
Laurynas Biveinis | |||
5.7 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hi,
Upgrading servers from 5.5.48-
2-node master-master setup (slaves of each other).
Upgraded secondary master. Replication broke on the primary master as per known bug, which is fine: https:/
Fixed and then upgraded primary master. This time replication broke on the secondary master, with a new error I've not seen before (didn't happen when upgrading the secondary master):
160708 0:43:49 [ERROR] Slave SQL: Error 'Storage engine 'InnoDB' does not support system tables. [mysql.servers]' on query. Default database: 'mysql'. Query: 'CREATE TABLE IF NOT EXISTS servers ( Server_name char(64) NOT NULL DEFAULT '', Host char(64) NOT NULL DEFAULT '', Db char(64) NOT NULL DEFAULT '', Username char(64) NOT NULL DEFAULT '', Password char(64) NOT NULL DEFAULT '', Port INT(4) NOT NULL DEFAULT '0', Socket char(64) NOT NULL DEFAULT '', Wrapper char(64) NOT NULL DEFAULT '', Owner char(64) NOT NULL DEFAULT '', PRIMARY KEY (Server_name)) CHARACTER SET utf8 comment='MySQL Foreign Servers table'', Error_code: 1726
160708 0:43:49 [Warning] Slave: Storage engine 'InnoDB' does not support system tables. [mysql.servers] Error_code: 1726
160708 0:43:49 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.001200' position 7180
I had to skip this statement, and *then* the usual one about 'You cannot 'ALTER' a log table if logging is enabled'
Why would this have affected only the second master?
tags: | added: regression |
I also confirm that the 'system' table exists on both servers, storage engine MyISAM.