Alfonso,
Ok I see what you mean with altering the Hibernate dialect, but I do
not like the call procedure solution, I prefer the second one, is a
more clean sloution.
Is this fix included in the sequoia 3.1 beta?
No it is not in 3.0beta1 but available in CVS or latest nightly build
(from download section).
If we have several oracle db replicated by sequoia cluster. How can we
know that different inserts over the same table from different
computers and managed by different sequoia controller will not get the
same primary key ID and multicast this value to the others?
You need to define "dual" as a table accessed in write so that Sequoia
can take a write lock and properly order all your accesses.
Both queries are sent at the same time form different clients
insert into tableT rowA
managed by sequoiaA
requests OracleA
gets ID 5 on Oracle A ? then multicast?
No multicast happens before getting to OracleA. Query will arrive at
SequoiaA and will be multicast to SequoiaA and SequoiaB where it will
execute on the local backends.
insert into tableT rowB
managed by sequoiaB
requests OrableB
gets ID 5 on Oracle B? then multicast?
Same as above.
Are you using any totally ordered multicast algorithm? that prevents
this scenario?
Yes, the group communication is configured to provide a total order
multicast.
I would recommend that you look at the available presentations on
Sequoia at http://sequoia.continuent.org/Resources to get a better idea
of how this works.
Thanks for your interest in Sequoia,
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
