Hi Tyler,
From the messages you sent, it looks like the request fails
consistently on both backends. So it looks like the behavior is
consistent and you might have a race condition in your application that
can lead to the foreign key violation.
If the problem only occurs under a certain load, the delay introduced by
Sequoia might exacerbate some synchronization issues in the application.
You might be able to reproduce the issue with a standalone database if
you artificially load the node where the database is running.
Hope this helps,
Emmanuel
I got the following errors on a single Sequoia controller with two
backend nodes:
009-01-20 09:59:48,302 INFO controller.loadbalancer.RAIDb1 write
request 48348 failed:
Backend ABDR - BackendWorkerThread for backend 'cluster2' with RAIDb
level:1 failed (ERROR: insert or update on table "contactdetails"
violates f
oreign key constraint "fk5cbbce22494239c6"
Detail: Key (emailaddress)=(569596) is not present in table
"emailaddress".)
Backend ABDR - BackendWorkerThread for backend 'cluster1' with RAIDb
level:1 failed (ERROR: insert or update on table "contactdetails"
violates f
oreign key constraint "fk5cbbce22494239c6"
Detail: Key (emailaddress)=(569596) is not present in table
"emailaddress".)
2009-01-20 09:59:48,303 INFO
virtualdatabase.VirtualDatabaseWorkerThread.ABDR Error during command
execution (write request 48348 failed:
Backend ABDR - BackendWorkerThread for backend 'cluster2' with RAIDb
level:1 failed (ERROR: insert or update on table "contactdetails"
violates f
oreign key constraint "fk5cbbce22494239c6"
Detail: Key (emailaddress)=(569596) is not present in table
"emailaddress".)
Backend ABDR - BackendWorkerThread for backend 'cluster1' with RAIDb
level:1 failed (ERROR: insert or update on table "contactdetails"
violates f
oreign key constraint "fk5cbbce22494239c6"
Detail: Key (emailaddress)=(569596) is not present in table
"emailaddress".)
It appeared to me that it is a result of previous query not executed
on one node before the next query gets executed. This error happens
randomly.
we managed to repeat this problem only when the server is running
under certain load. Also, FYI, WaitForCompletion policy is already set
to “all".
Any help is appreciated.
Tyler
------------------------------------------------------------------------
_______________________________________________
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
