Hi Thanks for the response. I'm doing replace into statements for the DB inserts. Show engine innodb status looks alright to me (although I'm not 100% sure what I'm looking for!).
Is there a way to alter the deadlock timeout? Cheers On 17/04/2012 05:30, "Ben Lisle" <[email protected]> wrote: >I'd check what is happening in MySQL land first (do a show engine >innodb status;). A lock often occurs when a transaction is not able >to complete within the deadlock timeout. Are you doing updates on a >column (rows are locked on indexes during those updates etc)? > > >On Thu, Apr 12, 2012 at 10:57 PM, Ian Mordey <[email protected]> >wrote: >> Hi there >> I'm attempting to use radiator backing off to a MySQL cluster running >>Galera >> replication. I have three radiator boxes and transactions are getting >> written to the DB but I'm getting lots of these errors: >> >> Deadlock found when trying to get lock; try restarting transaction >> >> Any ideas how I can stop this happening so much? >> >> Thanks >> >> _______________________________________________ >> radiator mailing list >> [email protected] >> http://www.open.com.au/mailman/listinfo/radiator _______________________________________________ radiator mailing list [email protected] http://www.open.com.au/mailman/listinfo/radiator
