The plan is the 3rd option, to achieve Fail Over capabilities.
There will be 2 or more servers running only Sequoia Controller,
pointing to a group of PostgreSQL backends each one. The application
server will use Sequoia JDBC Driver (not PostgreSQL JDBC anymore)
where those controllers will be spe
Hi Rodrigo,
So where did you install sequoia? On your application servers? On
your database servers? Or on dedicated servers running only sequoia?
Thanks,
Brendan Duddridge | CTO | 403-277-5591 x24 | [EMAIL PROTECTED]
Cli
Brendam,
We started testing Sequoia last week, and it reached our expectatives
of High Availability and Load Balance. We still need to verify if the
performance is not so degradated due to multiple clusters updating.
What is the difference between Sequoia and p/cluster? I mean, the
latter is a co
Hello Rodrigo,
Have you (or anyone else on this list) had great success with
Sequoia? I've been reading a bit about it. It looks like it might
work for us for a high-availability solution. Do you think it's just
as good as using p/cluster? We're deploying to Mac OS X Server and it
looks l
We're on the same situation.
--> PGCluster
Actualy, we installed and tested PGCluster on UML (User Mode Linux)
environment and real distributed stations. There were a lot of
critical issues on it! For example, once a user tries to connect to an
unexisting database, the load balancer fails and nee
