Re: (ITS#5385) contextCSN not propagated in cascading syncrepl refreshAndPersist

[hyc@symas.com]

bgmilne@staff.telkomsa.net wrote:
> Full_Name: Buchan Milne
> Version: OPENLDAP_REL_ENG_2_3
> OS: Linux 2.6
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (196.15.129.131)
>
>
> One of our environments does cascading replication of one database (the master
> for the other databases in this environment is a syncrepl refreshAndPersist
> syncrepl client to a database in another environment).
>
> We monitor the replication status of all our slaves by comparing the contextCSN
> on each database with the contextCSN of the updateref, and I have noticed that
> the contextCSN on the cascaded replicas is not being updated, even though the
> entries have been replicated (according to logging at sync level on these
> slaves). All other replication (including non-cascaded refreshAndPersist
> databases) works fine. All the servers in question are currently on 2.3.40.
>
> It seems that the issue can be reproduced with current REL_ENG_2_3, with a
> slight modification to test019 (see patch below) to include the contextCSN in
> the comparison, which will then fail as follows:

I've reproduced this issue in RE23 as well. I note that there's no such 
problem with RE24. If we can't track this down easily I'm inclined to just 
ignore 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/