Re: syncrepl refresh not finished after consumer restart

[Andreas Hasenack <ahasenack@terra.com.br>]

On Wed, Jul 19, 2006 at 03:24:22PM +0200, Halbritter, Matthias wrote:
> closed connection. When I start the consumer again, it starts in the
> REFRESH_DELETE mode, although it hasn't replicated all entries yet.
> Shouldn't the consumer finish or restart the refresh?

I'm getting the same behaviour here with 2.3 from yesterday's CVS. The consumer
starts in LDAP_RES_INTERMEDIATE - REFRESH_DELETE and doesn't get the new
stuff.

> The same behaviour when starting syncrepl with already-in-sync databases on
> provider and consumer, i.e.: When deleting a tree on the provider, the
> consumer starts deleting the same entries. When restarting the consumer
> *during* the deletions, syncrepl will restart in REFRESH_DELETE, although
> not all deletions had been passed on to and processed by the consumer.
> 
> Am I missing something or is this in fact intended behaviour which may leave
> me two inconsistent servers when the consumer is stopped or crashes during
> sync operations?

I'm getting replication problems without restarting the consumer during the
replication. I'm using the glue overlay, which I suspect is complicating
things.