[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Initial syncreplication details
- To: Marc Roos <M.Roos@f1-outsourcing.eu>, openldap-technical <openldap-technical@openldap.org>
- Subject: RE: Initial syncreplication details
- From: Quanah Gibson-Mount <quanah@symas.com>
- Date: Sat, 17 Aug 2019 11:40:49 -0700
- Content-disposition: inline
- In-reply-to: <"H00000710014c517.1566064364.sx.f1-outsourcing.eu*"@MHS>
- References: <"H00000710014c517.1566064364.sx.f1-outsourcing.eu*"@MHS>
--On Saturday, August 17, 2019 8:52 PM +0200 Marc Roos
<M.Roos@f1-outsourcing.eu> wrote:
I am not sure if this is true. Because it looks like provider and
consumer are a bit to long on high load for the changes that were made.
a) Don't use standard syncrepl, use delta-syncrepl
b) Don't use 2.4.44 with replication
c) If the slapcat contains a contextCSN, then it will be present on import.
I.e., you need to slapcat from a server that already has replication
enabled (generally best if it is a master)
d) Ensure that your export is younger than the expiry time on the accesslog
database configuration for delta-syncrepl. I.e., if the accesslog keeps 1
week of changes, ensure what you're importing is less than a week old, etc.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>