|
To be more complete, In my last test: The Application hangs because it
can't find a record which has been previously inserted. There was no failure when inserting this record, but it looks like Sequoia is atempting to use a disabled backend to serve some queries as you can see in the result of a "show backend *" command: +--------------------------+-------------------------------------+ | Backend Name | sd01 | | Driver | com.mysql.jdbc.Driver | | URL | jdbc:mysql://192.168.22.192/matisse | | Active transactions | 38 | | Pending Requests | 0 | | Read Enabled | false | | Write Enabled | false | | Is Initialized | true | | Static Schema | false | | Connection Managers | 2 | | Total Active Connections | 38 | | Persistent Connections | 0 | | Total Requests | 507 | | Total Transactions | 147 | | Last known checkpoint | <unknown> | +--------------------------+-------------------------------------+ | Backend Name | sd02 | | Driver | com.mysql.jdbc.Driver | | URL | jdbc:mysql://192.168.22.193/matisse | | Active transactions | 0 | | Pending Requests | 0 | | Read Enabled | true | | Write Enabled | true | | Is Initialized | true | | Static Schema | false | | Connection Managers | 2 | | Total Active Connections | 20 | | Persistent Connections | 0 | | Total Requests | 573 | | Total Transactions | 146 | | Last known checkpoint | <unknown> | +--------------------------+-------------------------------------+ As you can see, there are 38 active transactions on a disabled backend. No log shows that the backend has been disabled. Gérard BUNEL a écrit : Hello, We're currently facing some strange behavior of our application which insert a bunch of data in MySQL 5.0.37 databases, through Sequoia LoadBalancing (round-robin). We use Hibernate 3.1, MySQL Connector 5.0.4, Sequoia 2.10.6 under Linux RH Update 4Sometimes some data is inserted in only one backend and not the other, while Sequoia consider both enabled. Sometimes, the application hang on a data insertion, one of the backend is disabled. Then trying to stop the VDB hangs because of pending transactions. In this last case I've just seen the following log in the full_cluster.log 2007-06-27 16:59:46,067 WARN controller.RequestManager.MATISSEDB Ignoring failure of rollback for read-only transaction, exception was: java.sql.SQLException: Request rollback 151 has timed out (0 success - 0 failures) Does anyone has ever already encountered such situation ? Urgent help needed, we have a deadline in July. Thanks Gerard -- *Gérard BUNEL *Chef de Projet ____________________________________________________________________ Technopôle Brest Iroise Site du Vernis – CS 23866 29238 Brest Cedex 3 Tél : + 33 2 98 05 43 21 Fax : + 33 2 98 05 20 34 www.altran.com <http://www.altran.com> --
Gérard
BUNEL |
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
