[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Restarting syncrepl based provider / consumer setup trawls through whole DIT - why?
- To: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
- Subject: RE: Restarting syncrepl based provider / consumer setup trawls through whole DIT - why?
- From: Ole Nomann Thomsen <ole.nomann@stil.dk>
- Date: Tue, 25 Sep 2018 14:58:53 +0000
- Accept-language: da-DK, en-US
- Content-language: da-DK
- Thread-index: AdRU37OE3VOynowXQd+WMtmKZS53Fw==
- Thread-topic: Restarting syncrepl based provider / consumer setup trawls through whole DIT - why?
> --On Monday, September 24, 2018 2:51 PM +0000 Ole Nomann Thomsen
> <ole.nomann@stil.dk> wrote:
>
> > 2018-09-12T16:25:41.526574+02:00 nonpresent_callback: rid=001 present
> > UUID 9b99ec5a-4cfe-1029-9a2e-80309636f032, dn
> > ou=Authentication,o=UNI-C,c=DK
>
> This is the presence phase.
>
>
> > I'm guessing that that the Consumer is looking up every entry to decide
> > if it has changed.
>
> It is confirming each entry is still present (not deleted).
>
>
> > But why is it not persistent? Am a missing some obvious explanation as to
> > why this is not possible, or have I just misconfigured something? Any
> > hints where I should look?
> >
> > Is there a better way to set up replication to avoid this?
>
> a) Use delta-syncrepl
> b) Ensure you have a large sessionlog setting (See ITS#8125, ITS#8486)
>
> Warm regards,
> Quanah
Thanks - You too.
In my case, the present-phase is not really useful, since this particulat ldap-instance only ever adds and modifies entries, never deletes. Would it then be possible to skip it ?
- Ole.