[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#4423) syncrepl'd MODs cause DELs

Aaron Richton wrote:
> Additional log available
> https://www.nbcs.rutgers.edu/~richton/nonpresent/testrun.its4423.followup6.tar.gz
> Entry cn=Dorothy Stevens,ou=Alumni Association,ou=People,dc=example,dc=com
> CSN 20060427211935Z#000009#00#000000 greater than snapshot
> 20060427211935Z#000008#00#000000
> for a
> syncrepl_del_nonpresent: be_delete cn=Dorothy Stevens,ou=Alumni
> Association,ou=People,dc=example,dc=com (0)
What you're seeing in this trace is that new modifications arrived while 
the refresh is in progress; the Dorothy Stevens entry is correctly 
omitted from the Present list because it was modified more recently than 
the consumer's CSN.  We snapshot the provider CSN at the beginning of 
the refresh and only send entries where consumerCSN < entryCSN <= 
snapshot CSN, any subsequent mods must be picked up on the next Refresh 
pass. We use this snapshot mechanism because otherwise there's no way to 
set an endpoint for the search results. Note that the trace shows things 
working as intended, the Dorothy Stevens entry is propagated on the 
following Refresh pass.

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