Consistency "compromized" while update to Revive AdServer 4 and cosmetic issues

Bug #1634018 reported by Ville Ojamo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
New
Undecided
Unassigned

Bug Description

Percona XtraDB Cluster 5.5.28:
Percona-XtraDB-Cluster-server-56-5.6.28-25.14.1.el6.x86_64
Percona-XtraDB-Cluster-galera-3-3.14-1.rhel6.x86_64

Updating the Revive AdServer application to 4.0.0 caused a "consistency compromized" (sic), see below for log excerpt.

We are using enforce_storage_engine=InnoDB and I just noticed that wsrep_replicate_myisam=OFF, which according to docs is a not supported configuration. I do not know if the "consistency compromized" (sic) was caused by to that limitation. I have reluctantly enabled wsrep_replicate_myisam and will see if the problem goes away.

Is enforce_storage_engine safe in general? Which one is more safe, enforce_storage_engine=InnoDB or wsrep_replicate_myisam=ON?

Even if the compromise was caused by enforce_storage_engine & wsrep_replicate_myisam incompatibility, I want to raise three small cosmetic issues:

1- Typo on the error message:
"Node consistency compromized, aborting..."
Should probably be:
"Node consistency compromised, aborting...

2- MySQL log truncates the problem query annoyingly. In the log below it can be seen that the error query "CREATE TABLE [...]" is truncated and the log does not show the actual error in the query, somewhere "near 'TYPE=InnoDB'". This makes it difficult to work out what exactly happened. If the statement log length cannot default to a very_large_value, could there be a tunable that can be configured so the admin can make the decision how much of the query to log?

3- Retry counter is not following English:
"
Retrying 2th time
Retrying 3th time
Retrying 4th time
"
Should probably be "1st", "2nd", "3rd" or simply just:
"Retrying, attempt (number)"

==

Log:

2016-10-17 13:47:25 1105 [ERROR] Slave SQL: Error 'You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB' at line 42' on query. Default database: 'db_revive_adserver_400'. Query: 'CREATE TABLE `ox_z_2e11e043b90f08ed` (
  `bannerid` mediumint(9) NOT NULL DEFAULT '0',
  `campaignid` mediumint(9) NOT NULL DEFAULT '0',
  `contenttype` enum('gif','jpeg','png','html','swf','dcr','rpm','mov','txt') NOT NULL DEFAULT 'gif',
  `pluginversion` mediumint(9) NOT NULL DEFAULT '0',
  `storagetype` enum('sql','web','url','html','network','txt') NOT NULL DEFAULT 'sql',
  `filename` varchar(255) NOT NULL DEFAULT '',
  `imageurl` varchar(255) NOT NULL DEFAULT '',
  `htmltemplate` text NOT NULL,
  `htmlcache` text NOT NULL,
  `width` smallint(6) NOT NULL DEFAULT '0',
  `height` smallint(6) NOT NULL DEFAULT '0',
  `weight` tinyint(4) NOT NULL DEFAULT '1',
  `seq` tinyint(4) NOT NULL DEFAULT '0',
  `target` varchar(16) NOT NULL DEFAULT '',
  `url` text NOT NULL,
  `alt`
2016-10-17 13:47:25 1105 [Warning] WSREP: RBR event 2 Query apply warning: 1, 4170590643
2016-10-17 13:47:25 1105 [Warning] WSREP: Failed to apply app buffer: seqno: 4170590643, status: 1
         at galera/src/trx_handle.cpp:apply():351
Retrying 2th time
2016-10-17 13:47:25 1105 [ERROR] Slave SQL: Error 'You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB' at line 42' on query. Default database: 'db_revive_adserver_400'. Query: 'CREATE TABLE `ox_z_2e11e043b90f08ed` (
  `bannerid` mediumint(9) NOT NULL DEFAULT '0',
  `campaignid` mediumint(9) NOT NULL DEFAULT '0',
  `contenttype` enum('gif','jpeg','png','html','swf','dcr','rpm','mov','txt') NOT NULL DEFAULT 'gif',
  `pluginversion` mediumint(9) NOT NULL DEFAULT '0',
  `storagetype` enum('sql','web','url','html','network','txt') NOT NULL DEFAULT 'sql',
  `filename` varchar(255) NOT NULL DEFAULT '',
  `imageurl` varchar(255) NOT NULL DEFAULT '',
  `htmltemplate` text NOT NULL,
  `htmlcache` text NOT NULL,
  `width` smallint(6) NOT NULL DEFAULT '0',
  `height` smallint(6) NOT NULL DEFAULT '0',
  `weight` tinyint(4) NOT NULL DEFAULT '1',
  `seq` tinyint(4) NOT NULL DEFAULT '0',
  `target` varchar(16) NOT NULL DEFAULT '',
  `url` text NOT NULL,
  `alt`
2016-10-17 13:47:25 1105 [Warning] WSREP: RBR event 2 Query apply warning: 1, 4170590643
2016-10-17 13:47:25 1105 [Warning] WSREP: Failed to apply app buffer: seqno: 4170590643, status: 1
         at galera/src/trx_handle.cpp:apply():351
Retrying 3th time
2016-10-17 13:47:25 1105 [ERROR] Slave SQL: Error 'You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB' at line 42' on query. Default database: 'db_revive_adserver_400'. Query: 'CREATE TABLE `ox_z_2e11e043b90f08ed` (
  `bannerid` mediumint(9) NOT NULL DEFAULT '0',
  `campaignid` mediumint(9) NOT NULL DEFAULT '0',
  `contenttype` enum('gif','jpeg','png','html','swf','dcr','rpm','mov','txt') NOT NULL DEFAULT 'gif',
  `pluginversion` mediumint(9) NOT NULL DEFAULT '0',
  `storagetype` enum('sql','web','url','html','network','txt') NOT NULL DEFAULT 'sql',
  `filename` varchar(255) NOT NULL DEFAULT '',
  `imageurl` varchar(255) NOT NULL DEFAULT '',
  `htmltemplate` text NOT NULL,
  `htmlcache` text NOT NULL,
  `width` smallint(6) NOT NULL DEFAULT '0',
  `height` smallint(6) NOT NULL DEFAULT '0',
  `weight` tinyint(4) NOT NULL DEFAULT '1',
  `seq` tinyint(4) NOT NULL DEFAULT '0',
  `target` varchar(16) NOT NULL DEFAULT '',
  `url` text NOT NULL,
  `alt`
2016-10-17 13:47:25 1105 [Warning] WSREP: RBR event 2 Query apply warning: 1, 4170590643
2016-10-17 13:47:25 1105 [Warning] WSREP: Failed to apply app buffer: seqno: 4170590643, status: 1
         at galera/src/trx_handle.cpp:apply():351
Retrying 4th time
2016-10-17 13:47:25 1105 [ERROR] Slave SQL: Error 'You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB' at line 42' on query. Default database: 'db_revive_adserver_400'. Query: 'CREATE TABLE `ox_z_2e11e043b90f08ed` (
  `bannerid` mediumint(9) NOT NULL DEFAULT '0',
  `campaignid` mediumint(9) NOT NULL DEFAULT '0',
  `contenttype` enum('gif','jpeg','png','html','swf','dcr','rpm','mov','txt') NOT NULL DEFAULT 'gif',
  `pluginversion` mediumint(9) NOT NULL DEFAULT '0',
  `storagetype` enum('sql','web','url','html','network','txt') NOT NULL DEFAULT 'sql',
  `filename` varchar(255) NOT NULL DEFAULT '',
  `imageurl` varchar(255) NOT NULL DEFAULT '',
  `htmltemplate` text NOT NULL,
  `htmlcache` text NOT NULL,
  `width` smallint(6) NOT NULL DEFAULT '0',
  `height` smallint(6) NOT NULL DEFAULT '0',
  `weight` tinyint(4) NOT NULL DEFAULT '1',
  `seq` tinyint(4) NOT NULL DEFAULT '0',
  `target` varchar(16) NOT NULL DEFAULT '',
  `url` text NOT NULL,
  `alt`
2016-10-17 13:47:25 1105 [Warning] WSREP: RBR event 2 Query apply warning: 1, 4170590643
2016-10-17 13:47:25 1105 [ERROR] WSREP: Failed to apply trx: source: c748a94c-434c-11e6-bc00-0b5c3edceafd version: 3 local: 0 state: APPLYING flags: 129 conn_id: 527953888 trx_id: 10189728206 seqnos (l: 492707161, g: 4170590643, s: 4170590642, d: 4170590642, ts: 21435277002486328)
2016-10-17 13:47:25 1105 [ERROR] WSREP: Failed to apply trx 4170590643 4 times
2016-10-17 13:47:25 1105 [ERROR] WSREP: Node consistency compromized, aborting...
2016-10-17 13:47:25 1105 [Note] WSREP: Closing send monitor...
2016-10-17 13:47:25 1105 [Note] WSREP: Closed send monitor.
2016-10-17 13:47:25 1105 [Note] WSREP: gcomm: terminating thread
2016-10-17 13:47:25 1105 [Note] WSREP: gcomm: joining thread
2016-10-17 13:47:25 1105 [Note] WSREP: gcomm: closing backend

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/PXC-1934

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

Other bug subscribers

Remote bug watches

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