Hi
Let me describe the workaround what we are using for that.
First, few word how bucardo sync is working:
To populate changes, bucardo is creating on every node and is using:
* delta tables - to store local changesets
* track tables - to store information on already propagated changes
in later failover scenario we can remove entries from track tables
to force sync them one more time.
we don't have to worry about duplicates because of ... bucardo built-in
standard conflict resolution?? (working in practice)
Workaround what we are using is:
* store tx_time of of latest delta sync
* update dbgroup to remove broken node
and after node is repaired
* add new node to db group
* remove entries in track tables older than stored tx_time.
* enjoy synced data
One might be interested in set vac_sleep time respectively bigger, as
after that time delta tables will be cleaned.
Cheers.
Błażej
On 12/04/2013 12:38 PM, Jonathan Brinkman wrote:
I agree this is a huge problem. I have a master with 20 slaves in a dbgroup,
using bucardo 4.5, and if any one of the slaves goes offline then ALL syncs
break, even those that have nothing to do with the missing slave or that
dbgroup. This seriously undermines the value of bucardo... and it is very
uncomfortable explaining to our clients why all the syncs are stopped until
someone goes to fix the offline slave server.
Is this fixed in bucardo 5?
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Tuesday, December 03, 2013 7:00 AM
To: [email protected]
Subject: Bucardo-general Digest, Vol 75, Issue 3
Send Bucardo-general mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://mail.endcrypt.com/mailman/listinfo/bucardo-general
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific than
"Re: Contents of Bucardo-general digest..."
Today's Topics:
1. Master to multi slave replication ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Mon, 2 Dec 2013 21:04:25 +0000
From: <[email protected]>
To: <[email protected]>
Subject: [Bucardo-general] Master to multi slave replication
Message-ID:
<940b3e4466e3ed43bf83e983939436660e7e2...@simtcsmb11.napa.ad.etn.com>
Content-Type: text/plain; charset="us-ascii"
Hi everyone,
I have the following configuration: one master (with the name C) and 3 slave
servers (names are SL1, SL2, SL3), what installed to maintain pushdelta
replication from the master. I added all tables from master database to 3
herds with names H1, H2 and H3 and made 3 syncs ( bucardo_ctl add sync S1
source=H1 type=pushdelta targetdb=SL1; bucardo_ctl add sync S2 source=H1
type=pushdelta targetdb=SL2; bucardo_ctl add sync S3 source=H1
type=pushdelta targetdb=SL3). And everything was working fine until one of
slave server went offline. I noticed that 2 online slave servers stop
receiving replication from the master.
Is that possible to make replication working with remaining 2 slave servers?
Can that be done automatically by bucardo_ctl process?
My enviropment:
CentOS6.4 64bit, bucardo 4.4.7, postgres 9.3
Thank you for help!
Alexander
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20131202/d5
337cfa/attachment-0001.html>
------------------------------
_______________________________________________
Bucardo-general mailing list
[email protected]
https://mail.endcrypt.com/mailman/listinfo/bucardo-general
End of Bucardo-general Digest, Vol 75, Issue 3
**********************************************
_______________________________________________
Bucardo-general mailing list
[email protected]
https://mail.endcrypt.com/mailman/listinfo/bucardo-general
_______________________________________________
Bucardo-general mailing list
[email protected]
https://mail.endcrypt.com/mailman/listinfo/bucardo-general
