Mon Apr 21 08:52:03 PDT 2008
- Previous message: [Slony1-general] Slony Replication in wide-area applications?
- Next message: [Slony1-general] Catching up a large backlog: a few observations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Apr 20, 2008, at 5:48 AM, Michael Gruetzner wrote: > The Slony-1 documetation says that it might not be suitable if some > nodes may > fail oftenly but it does not explain how slony deals with such > failures (maybe someone > can explain this to me?). > Slony deals well with hosts which go offline for a bit. The problem lies with the amount of change your DB has. If you're doing millions of updates per day, then slony has to queue up all those changes to apply later. If your WAN can handle that much data flying across, you're ok. It must also be able to handle your normal volume plus any backlog updates that slony needs to apply. > So what I'm asking is: Does anyone have experience with Slony-1 and > wide area > clusters? I do, but the one application that I do this for has perhaps a dozen insert/update/delete per day. Having four or five day downtime is a total non-issue for this case. I only do it with two nodes.
- Previous message: [Slony1-general] Slony Replication in wide-area applications?
- Next message: [Slony1-general] Catching up a large backlog: a few observations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list