[Pgcluster-general] Last chance to get everything working
John Gardner
john.gardner at tagish.co.uk
Wed May 23 08:46:17 UTC 2007
I've been working with pgCluster for the last four months now, I'm at
the stage where we need to install it in a production environment, but I
must say that I'm still apprehensive about a few things, some things
certainly don't work in my environment. I have chatted with Rick Vernam
about a few of these problems, and although we seem to have the same
configuration, his works and mine doesn't.
My configuration is this:
DB 1 DB 2 DB 3
+--------------+ +--------------+ +--------------+
| cluster_1 | | cluster_2 | VPN | cluster_3 |
| rep_1 |---| rep_2 |------------------| rep_3 |
| lb_1 | | lb_2 | | |
+--------------+ +--------------+ +--------------+
| |
| |
+--------------+ +--------------+
| Apache | | Apache |
| mod_jk | | mod_jk |
| Tomcat |---| Tomcat |
+--------------+ +--------------+
APP 1 APP 2
My problems are:
- Replication works between all of the nodes under normal circumstances.
- Multiple replicator failover doesn't work.
- Occasionally when bringing a DB Cluster node back up in recovery mode,
access to the remaining DB clusters locks and I can't access anything
either via the load balancer or directly.
- Does <Response_Mode> have any use at all? One of the reasons for going
down the pgCluster route was the 'normal' operation, but I've just read
a post on the mailing list from Atsushi saying that normal operation
doesn't work and should be removed.
- What is the difference of setting <Use_Replication_Log> to yes or no?
We really, have to make a decision this week, whether we stick with
pgCluster or go via another route. I've stuck with pgCluster for this
long because I was convinced that the reason it was not performing as I
had expected was due to configuration errors, but now I'm not so sure...
If anyone can give me any help I would be extremely grateful!
Thanks in advance
John
More information about the Pgcluster-general
mailing list