pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: RW <postgres@tauceti.net>
To: CG <cgg007@yahoo.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Pg/CyberCluster test results
Date: Fri, 22 Aug 2008 15:52:39 +0200
Message-ID: <48AEC4A7.6050508@tauceti.net> (raw)
In-Reply-To: <767392.31997.qm@web37902.mail.mud.yahoo.com>
References: <767392.31997.qm@web37902.mail.mud.yahoo.com>

I hoped that it would be easier to get the nodes back in sync
but it seems that all Postgres Multi-Master solutions are not
reliable at the moment. I've planed to test CyberCluster
this weekend but I already suspected that this rsync solutions
have some shortcomings. Sniff...

It seems that we have to wait for PGCluster-II which isn't a
"shared nothing" solution. Instead all files are on a shared
medium like SAN or iSCSI and all instances uses this medium
(similar to Oracle).

Robert

CG wrote:
> I've been testing Cybercluster (which is a modified PgCluster) ... I have two back-end databases, one load balancer, and one replicator. I've been testing failover and rebuilding a degraded cluster, and I'm finidng that it is REALLY easy for the two back-ends to get out of sync with each other. This is very disturbing. I was wondering if anyone has experience with solving this problem.
>
>
>       
>
>   




view thread (5+ messages)  latest in thread

Message-ID: <48AEC4A7.6050508@tauceti.net>
Permalink:  ../48AEC4A7.6050508@tauceti.net/
Also on:    postgresql.org/message-id/48AEC4A7.6050508@tauceti.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: postgres@tauceti.net, cgg007@yahoo.com
  Subject: Re: Pg/CyberCluster test results
  In-Reply-To: <48AEC4A7.6050508@tauceti.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox