Normally I would not advice upgrade unless you know there is a fix, or similar, but in this case I doubt if it would be a good idea to try.
It will probably happen to you on the next upgrade. I raised a bug report for this months ago:
https://bugs.launchpad.net/percona-server/+bug/1600056
Looks to me like between the releases 5.5.48-rel37.8-1 and 5.5.49-rel37.9-1, something was changed.
Note the error is on 'CREATE TABLE IF NOT EXISTS' and doesn't specify the engine MyISAM, so it probably tries InnoDB first.
What I think is going on is that that query always ran, but only in that 5.5.49 release did Percona/MySQL get strict about reporting that as an error and aborting.
The slave sees the query in the binary logs from the master and tries to run it, and fails.
So hence why it very well might occur on your next upgrade again.
I note that in the release notes [1] for that Percona release, one bug fixed is 'CREATE TABLE ... LIKE ... could create a system table with an unsupported enforced engine. Bug fixed #1540338.' << could be this caused a regression by tightening that logic.
Would be great if the Percona devs could look into it, my bug has gone unanswered for months!
[1] https://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.49-37.9.html
Rebuilt the mysql replication with upgraded percona server 5.5.52-38.3. It has been running for a day and so far no issue.Thanks all for your help
On Tuesday, September 20, 2016 at 7:02:21 PM UTC-4, Roel Van de Paar wrote:.Yes, and more specifically in;Percona Server 5.5.52-38.3Percona Server 5.6.33-78.2
On Tuesday, September 20, 2016 at 3:34:09 PM UTC+10, migue...@codeenigma.com wrote:On Monday, 19 September 2016 23:01:49 UTC+10, Asif Iqbal wrote:
> Yep it happended again...
I think it will be fixed on the next release, it's already fixed in Git.
Cheers
--
You received this message because you are subscribed to a topic in the Google Groups "Percona Discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/percona-discussion/2eZtWaqTMPM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to percona-discussion+unsub...@googlegroups.com.
To post to this group, send email to percona-discussion@googlegroups.com.
Visit this group at https://groups.google.com/group/percona-discussion.
To view this discussion on the web visit https://groups.google.com/d/msgid/percona-discussion/efb724fe-ceb2-4f72-8f10-8bc9b0e1f2a0%40googlegroups.com.
On Mon, Oct 17, 2016 at 11:02 AM, Asif Iqbal <vad...@gmail.com> wrote:Rebuilt the mysql replication with upgraded percona server 5.5.52-38.3. It has been running for a day and so far no issue.Thanks all for your helpLooks like the issue came back.I am usingServer version: 5.5.52-38.3-log Percona Server (GPL), Release 38.3, Revision 109ad68....Slave_IO_Running: YesSlave_SQL_Running: No......Last_SQL_Error: 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''Should I need to upgrade the percona mysql server?I am running it on centos 6.8 x86_64