[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#4622) syncrepl operations incomplete when consumer restarted

I don't understand what issue you're reporting. The syncrepl consumer 
always restarts when the consumer server is stopped and restarted. What 
does REFRESH_DELETE have to do with anything?

matthias.halbritter@faedv-n.bayern.de wrote:
> Full_Name: Matthias Halbritter
> Version: 2.3.17 & 2.3.24
> OS: SuSE Linux Enterprise Server 9
> URL: 
> Submission from: (NULL) (
> Changes int the provider's database are not fully passed on to the consumer when
> it is restarted. The consumer then has only processed the sync operations up to
> the stopping of the consumer. After restarting the consumer it will show
> REFRESH_DELETE in debug mode although not all changes had been passed on and
> processed. The consumer should finish or at least restart the sync operations.
> The least should be a warning that there have been some problems.
> Behaviour is reproducible with OpenLDAP 2.3.17 and 2.3.24. Behaviour is
> reproducible in syncrepl refreshOnly mode (consumer restart during refresh) and
> in syncrepl refreshAndPersist mode (consumer restart during refresh, consumer
> restart during sync operations).
> See also: mailing list openldap-software entry titled "syncrepl refresh not
> finished after consumer restart" from Wed July 19th 2006.
> I could do with having to start syncrepl with databases on provider and consumer
> that have to be synchronized when starting syncrepl (that's how it's always been
> with slurpd). I cannot, however, find proper use for syncrepl when I cannot be
> sure whether all changes are properly passed on and processed.

  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc
  OpenLDAP Core Team            http://www.openldap.org/project/