[Bucardo-general] Sync stops when one servers fails

Greg Sabino Mullane greg at endpoint.com
Mon Oct 19 16:09:31 UTC 2015


On Fri, Oct 16, 2015 at 03:08:01PM +0000, Johan Peeters wrote:
> We have a 3 DB's setup in master-master environment.
...
> I think the scenario when a server fails should be like this:
> -  the synchronization between the other running servers continues
> -- the failed server should be deactivated in the sync (and have to be activated manually later) OR
> -- Bucardo tries to make connection to the failed one (and when its online sync the missing records)
> 
> Is there a workaround ?

No direct workaround, no. It is a known problem, with no easy solution, as
keeping track of which rows have been replicated to which fraction of
an existing sync is a tricky (but solveable) problem.

A future version will have a sync-level option that tells Bucardo to drive
on, continuing to replicate to what it can, and then autmatically cathching
the flaky servers back up once they come alive.

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20151019/28f261c7/attachment.sig>


More information about the Bucardo-general mailing list