As it turns out my backends were getting hung on shutdown, so my DB was in a "Suspending" state. Both controllers just keep printing out Waiting for 1 pending writes. Looking at the queues show a broken query stuck in there with no way to get it out (abort transaction didn't work). I had to force the DB down and then recover it. I seem to be able to replicate this by shoving a broken query into the backends, causes everything to get stuck open. Is there a fix for this?
-Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emmanuel Cecchet Sent: Wednesday, November 12, 2008 4:10 PM To: Sequoia general mailing list Subject: Re: [Sequoia] Failover Failure? Hi Eric, Can you check that the backend on the active controller is still enabled? What JDBC URL do you use in your application? Thanks for your interest in Sequoia, Emmanuel > I currently have two machines, each with a MySQL Instance and > Sequoia instance. They are configured such that the controllers > mirror the two MySQL Instance (box 1 has box 1's mysql as backend, > etc). When I shutdown the virtual database on box 1 or box 2 the > entire cluster now fails to function or write any data. I get the error > > "create table test (I int)/' failed on all controllers. If I bring > back up the second controller it all works again. Any ideas? > > > > -Eric > > ------------------------------------------------------------------------ > > _______________________________________________ > Sequoia mailing list > [email protected] > https://forge.continuent.org/mailman/listinfo/sequoia -- Emmanuel Cecchet FTO @ Frog Thinker Open Source Development & Consulting -- Web: http://www.frogthinker.org email: [EMAIL PROTECTED] Skype: emmanuel_cecchet _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
