Dropping a MyISAM table after inserting a user variable breaks bi-directional replication

[GoogleCodeExporter]

Using a bi-directional topology, (host1: master[alpha], slave[bravo], host2: 
master[bravo], slave[alpha]), replication breaks if you use a MyISAM table in 
combination with a user variable

USE test;
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (ccc char(100)) ENGINE=myisam;
SET @ccc = '';
INSERT INTO t1 values (@ccc);
drop table t1;

Using innodb instead of MyISAM will make the commands succeed always.

Dropping the table without having used a user variable also succeds.

trepctl -host qa.r2.continuent.com -service alpha status
Processing status command...
NAME VALUE
---- -----
appliedLastEventId : NONE
appliedLastSeqno : -1
appliedLatency : -1.0
clusterName : qatest
currentEventId : NONE
currentTimeMillis : 1301579733619
dataServerHost : qa.r2.continuent.com
extensions :
host : null
latestEpochNumber : -1
masterConnectUri : thl://qa.r1.continuent.com:2112/
masterListenUri : thl://qa.r2.continuent.com:2112/
maximumStoredSeqNo : -1
minimumStoredSeqNo : -1
offlineRequests : NONE
pendingError : Event application failed: seqno=20 fragno=0 
message=java.sql.SQLException: Statement failed on slave but succeeded on master
pendingErrorCode : NONE
pendingErrorEventId : 000002:0000000000006996;843
pendingErrorSeqno : 20
pendingExceptionMessage: java.sql.SQLException: Statement failed on slave but 
succeeded on master
resourcePrecedence : 99
rmiPort : -1
role : slave
seqnoType : java.lang.Long
serviceName : alpha
serviceType : unknown
simpleServiceName : alpha
siteName : default
sourceId : qa.r2.continuent.com
state : OFFLINE:ERROR
timeInStateSeconds : 249.076
uptimeSeconds : 388.049

Note: migrated from TUC-307)

Original issue reported on code.google.com by g.maxia on 12 Jul 2011 at 7:07

[GoogleCodeExporter]

Original comment by berkeley...@gmail.com on 26 Aug 2011 at 1:02

• Added labels: Durability

[GoogleCodeExporter]

Original comment by berkeley...@gmail.com on 26 Aug 2011 at 4:11

• Changed title: Dropping a MyISAM table after inserting a user variable breaks bi-directional replication

[GoogleCodeExporter]

Original comment by stephane...@continuent.com on 5 Jun 2012 at 3:55