Hi Oliver
Actually these are the messages when we ran the test with 2 backends
(postgresql 8.14)
2006-09-28 14:25:00,796 INFO sequoia.controller.loadbalancer Deadlock
detected on backend testdb2, aborting transaction 13952628
2006-09-28 14:25:00,799 ERROR controller.loadbalancer.RAIDb1 write request
27947321 failed:
Backend testdb - BackendWorkerThread for backend 'testdb1' with RAIDb
level:1 failed (Transaction aborted due to deadlock)
Backend testdb - BackendWorkerThread for backend 'testdb2' with RAIDb
level:1 failed (Transaction aborted due to deadlock)
2006-09-28 14:25:00,800 INFO sequoia.controller.cache Flushing whole cache
due to rollback of transaction : 13952628
2006-09-28 14:25:00,800 WARN controller.virtualdatabase.abrazo Request
INSERT INTO table1 (TRANSACTIONI... failed, transaction has been aborted
(write request 27947321 failed:
Backend testdb - BackendWorkerThread for backend 'testdb1' with RAIDb
level:1 failed (Transaction aborted due to deadlock)
Backend abrazo - BackendWorkerThread for backend 'testdb2' with RAIDb
level:1 failed (Transaction aborted due to deadlock)
)
2006-09-28 14:25:00,800 WARN
virtualdatabase.VirtualDatabaseWorkerThread.testdb Error during command
execution (write request 27947321 failed:
Backend testdb - BackendWorkerThread for backend 'testdb1' with RAIDb
level:1 failed (Transaction aborted due to deadlock)
Backend testdb - BackendWorkerThread for backend 'testdb2' with RAIDb
level:1 failed (Transaction aborted due to deadlock)
)
2006-09-28 14:25:00,805 WARN backend.DatabaseBackend.testdb1 No transaction
medatada found for transaction 13952628 releasing locks manually
2006-09-28 14:25:00,807 WARN backend.DatabaseBackend.testdb2 No transaction
medatada found for transaction 13952628 releasing
So The messages in the previous e-mail is when we ran the test just with
one backend
The test still run, but is extremly slow with sequoia, I believe because of
the deadlock, however when we run the aplication without sequoia there is no
deadlock reported by postgresql.
Thanks
From: Olivier Fambon <[EMAIL PROTECTED]>
Reply-To: Sequoia general mailing list <[EMAIL PROTECTED]>
To: Sequoia general mailing list <[EMAIL PROTECTED]>
Subject: Re: [Sequoia] Sequoia 1.10 error messages
Date: Fri, 29 Sep 2006 10:08:37 +0200
Julio Leyva wrote [09/28/2006 11:23 PM]:
Hi all
Hi Julio,
We are testing an aplication on a volumen test bed using sequoia 2.10 and
one backend postgresql 8.14
We are seeing these error messages when we try to update or insert info in
our tables.
2006-09-28 16:55:05,315 DEBUG controller.RequestManager.abrazo Load
balancing write request (21006,6042): INSERT INTO table2(TRANSACTIONI...
2006-09-28 16:55:05,316 DEBUG controller.RequestManager.abrazo
Invalidating cache for write request (21006): INSERT INTO table2
(TRANSACTIONI...
2006-09-28 16:55:05,502 DEBUG controller.RequestManager.abrazo Load
balancing write request (21009,6043): Update table1 set current_...
2006-09-28 16:55:05,509 DEBUG controller.RequestManager.abrazo
Invalidating cache for write request (21009): Update table1 current_...
So we ran the same test just without sequoia and it works ok.
any ideas?
These are debug messages, not error messages.
Does your test actually fail ?
_______________________________________________
Sequoia mailing list
[EMAIL PROTECTED]
https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
[EMAIL PROTECTED]
https://forge.continuent.org/mailman/listinfo/sequoia
