Hi Neil,
I have read the Sequoia installation guide and
the JGroups users guide and have come up with a layout
to use for two geographically separate machines that
are interconnected via SSL tunnelled connections.
Be careful that you need to use a JGroups that provides total order like
the one defined in config/sequencer.xml. The config you provided does
not seem to implement total order.
For the database backends, each controller will use
these two URLs for each of their backends:
jdbc:mysql://localhost:3306
jdbc:mysql://localhost:3406
That way, each will have access to both databases.
Do the controllers need access to both of the databases
or does each use only its local copy?
No you cannot share a backend between multiple controllers. At any given
time, a backend can only be attached to a single controller. You might
want remote backend access in case you would like to transfer a backend
from one controller to another. However, the same url is supposed to be
used on every controller to access a backend (that would not work in
your case because the url is different is you access the backend locally
or remotely).
So I would recommend so skip the remote MySQL access and just stick with
local controller access.
Does this configuration look correct or did I miss
something?
If you ensure that you use total order for the group communication and
you don't share your backends, the config looks ok. Be aware that
Sequoia does not support network partitions (if your ssh tunnels go down
but both controllers are still working, your 2 sub-clusters will diverge
and cannot reconcile automatically).
Thanks for your interest in Sequoia,
Emmanuel
--
Emmanuel Cecchet
Chief Architect, 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
