Hi Quanah

   Thank you for the response.
If the consumer is several days behind and the accesslog does not have the data then fresh reload from the provider will happen automatically?

Thanks
Rahul

On Tue, Jul 14, 2020 at 11:28 AM Quanah Gibson-Mount <quanah@symas.com> wrote:
--On Friday, July 10, 2020 11:04 AM -0400 kumar rahul
<rahul2002mit@gmail.com> wrote:


> 1) What is the recommended value for olcSpCheckpoint?
> As per your blog value is olcSpCheckpoint: 20 10

I prefer to have it checkpoint fairly frequently, which is why I chose
those values.

> 2) What is the recommended value of olcAccessLogPurge?
> As per your blog value is olcAccessLogPurge: 01+00:00 00+04:00

So this depends specifically on the environment in question.  The more data
retained, the further back a replica can "catch up" to the provider(s) by
using delta-syncrepl.  However, the more data retained, the larger the
database will be.  Whether or not one wants a replica to be able to "catch
up" to a provider if it is several days behind vs reloading it with a fresh
copy of the db from the provider is the real question.

Regardless of the data retention period, I always suggest a frequent purge
interval.  This is because slapd essentially pauses while a purge is
ongoing.  For most environments, a 4 hour purge interval is not noticable.
I've gone to as frequent as every 2 hours for extremely active sites.

Regards,
Quanah

--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>