Re: (ITS#5378) hot slapcat for slapadd issues with delta-sync

[hyc@OpenLDAP.org]

quanah@OpenLDAP.org wrote:
> Full_Name: Quanah Gibson-Mount
> Version: 2.3.40
> OS: NA
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (24.23.156.219)
>
>
> If someone is using delta-syncrepl for replication, and does a hot slapcat of a
> server, and a change occurs during the slapcat, the resulting LDIF file cannot
> be used on a replica.  This is because the replica will try to resume from the
> CSN in the LDIF file, which is from before the change occurred.  Since the
> change is in the LDIF file, when the replica contacts the master, it tries to
> re-replicate the change (which obviously fails).  At that point, the replica is
> stuck and unable to progress.  The only guaranteed way to get a viable slapcat
> when using delta-syncrepl is to put the server being dumped into RO mode or to
> stop it.

Another possibility would be to filter out any entries whose entryCSNs are 
newer than the contextCSN in the LDIF before trying to slapadd it.

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