[389-users] Manual and automatic catch up of replication

[Gerrard Geldenhuis]

Hi
I have been doing some testing to see how a database(netscapedb) will catch up with replicated changes when the server has been shutdown and/or broken.

My test is very basic:
Shutdown master2
Add an entry to netscapedb on master1
Bring up master2
Tail error log for replication messages and check console on master2 for presence of data.

I know this is imprecise but my observation has been so far that if master2 was down for a short period of time it will automatically catch up but if it were down for a longer period of time (more than an hour) and I bring it up, new updates are not automatically send. I have to click on send updates in the 389-console for the latest changes to be reflected.

Is there more definitive rules that govern when a database will be updated automatically and when the process becomes manual?

Best Regards

________________________________________________________________________
In order to protect our email recipients, Betfair Group use SkyScan from 
MessageLabs to scan all Incoming and Outgoing mail for viruses.

________________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20100920/23853e1d/attachment.html>