Jan-willem,
When everything is up and running, I start a test script that will do
a lot of create/read/update/delete queries (on one table). The test
script is in Perl (like everything that uses the database here).
While this script is running I start the console on one backend, and
issue a disable backend.
The backend will then start its shutdown cycle, and complain about
open transactions, and that it will wait for 300 seconds for them to
finish.
When you disable a backend it will wait for currently open transactions
to complete but not start new transactions. Are you sure that your Perl
script commits or rollbacks every transaction and does not leave open
transactions?
I am not sure why this 300 seconds timeout was introduced, IMHO this is
a bad idea, this should only be an option and definitely not the default.
The transactions will not finish in that time, and then the backend
crashes.
Do you have any transaction that takes more than 5 minutes to complete?
Thanks for your feedback,
Emmanuel
--
Emmanuel Cecchet
Chief Scientific Officer, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
