Hi, I have a production env like this one : 5 web servers running the same java web app, behind a load balancer. 2 database servers
Currently, the database servers are running in a fail over configuration : only a single server is used, the other is just there is something wrong happens. Because we will migrate this to a master-master (mysql) replication design, I will need to load balance the queries on the two instances. How can I achieve this with Sequoia ? I've read a kind of configuration, called ParallelDB exists but is not well tested and there is no example in the sequoia distribution of this (only singleDB). My questions are : - is parallelDB strong enough to be used in a quite heavily stressed production env ? - is there any example of this kind of configuration ? - do I miss something that can be used to solve my problem (any other way to do this) ? Just to understand a little bit well how Sequoia can be used, let's imagine this architecture : 2 servers running each one a read only DB instance (which can be a slave in a replication scheme). Is it possible in this particular condition (2 read only instances, no sequoia replication, just LB) to use only the load balancing feature (parallelDB) this way : A controller (Ca), managing the two instances, is deployed on server A Another controller (Cb) is deployed on server B, managing the same two instances Ca and Cb are redundant and the controller layer isn't a single point of failure. Any advice is welcome. Thx _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
