RE: Initial syncreplication details

["Marc Roos" <M.Roos@f1-outsourcing.eu>]

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.


-----Original Message-----
Subject: Initial syncreplication details



Am I correct to understand from this page[0] that the consumer gets its 
'new' contextCSN from the slapcat import. (I saw it in the file). And 
will get all data since that date at startup? 

The replication id is of no influence. So if I would stop slapd import 
again the same old slapcat file. It would again receive all new data 
since that contextCSN? Regardless of the same rid being used with the 
provider.

The idea behind this is that if you create a container with a default 
imported slapcat/slapadd file. Every time the task is stopped and 
started. It will go back to it initial container state. (unless you make 
it statefull of course) I am not adding that much data so I could make a 
new default image every week or so, this would be used every time  a 
container is launched. 
(which only happens in a failover situation)

[0]
https://www.openldap.org/doc/admin24/replication.html