Hi Francois,
We have been using sequoia for about 3 years now and we are very
satisfied with the product. We are using 1 controller with 2
backends. We are now looking for a replication solution outside our
hosting center as a measure of disaster recovery. Basically we want
to know if it is feasible with sequoia to have a second controller
that could be accessed asynchronously. Ideally, write and update
requests are processed on the first controller that waits (in our
case) for both backends to come back. The second sequoia controller
could just process requests asynchronously, kind of fire and forget
which would effectively act as a replication system. Is this a
possible scenario with sequoia ?
One way of achieving that is to add a 3rd backend to your 1st
controller. This 3rd backend will in fact be the remote Sequoia
controller that you will access using the Sequoia driver. You have to
configure the load balancer WaitForCompletion policy to something else
than all so that you can achieve the asynchrony you need.
Another way is to use the group communication as if it were a regular
distributed virtual database, but use a simple UDP multicast or
tunneling through JMS (check what JGroups configuration are available)
to do this fire & forget.
For now that's all what is available for asynchronous replication in
Sequoia. I was planning on developing a recovery log shipping solution
for asynchronous replication between controllers, but I did not find the
time to do it so far.
Hope this helps,
Emmanuel
--
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
