MySQL Forums :: Replication :: Row based Replication: Deadlock is not rolled back


Advanced Search

Row based Replication: Deadlock is not rolled back
Posted by: Michael Moench ()
Date: April 29, 2010 10:51AM

I'm using MySQL 5.1.39 with a row based replication from my master to my slave.
The master is running with InnoDB-tables and the slave with MyISAM.

My Problem involves an insert statement on my master which has an after insert trigger. This after insert trigger is causing a deadlock with an other query I'm running which causes the master to rollback my insert and no data is modified on the master. The problem however is that the insert is written into the binary log which results in inconsistent data between master and slave.

This does only happen when I'm using row based replication. When I switch to statement based replication the insert statement that is terminated to resolve the deadlock is not logged.

Is this a known behavior and does anyone know how to prevent this (except not using row based replication)?

Options: ReplyQuote


Subject Views Written By Posted
Row based Replication: Deadlock is not rolled back 2226 Michael Moench 04/29/2010 10:51AM
Re: Row based Replication: Deadlock is not rolled back 991 Michael Moench 04/30/2010 03:09AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.