[Bucardo-general] support for loss of connectivity to slave server/slave db going down

[Greg Sabino Mullane]

> I have 2 master servers and 1 slave server.  The master servers have
...
> that have not been replicated (300k+ rows).  Now, I restart the
> postgresql-8.4 service on the slave and restart the burcado processes
> on the master servers.  I expected all the rows that haven't yet been
> replicated to the slave to be replicated over.  However, after a
> minute or so, the "catch-up" is done and there are rows that haven't
> been replicated-- 708586 across 2 master servers and 706191 on the
> slave server.  What happened to the other 2395 rows ?

Good question! Have you setup makedelta, so that changes from one master
to the other are receorded in the bucardo_delta table and thus ready to
go to the slave? If not, that's the problem.

> As a side question, other than having some sort of cron job on each
> master server that periodically checks for the burcado process and
> restarts it if it is dead, is there a more graceful way of supporting
> loss of connectivity/issues with the burcado process ?

Bucardo is setup to restart itself by default, so if it's not, that's a
bug we need to address.

-- 
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: OpenPGP digital signature
Url : https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20100120/a22a6a12/attachment.bin