Re: Sync replication failure during startup.

[Howard Chu <hyc@symas.com>]

Stelios Grigoriadis wrote:
> I have upgraded openldap to latest stable version (2.3.38) and
> used Berkeley DB version 4.5.20. The problem remains. I realize
> my analisys wasn't correct since, as Howard Chu pointed out, the
> CSN contains both a timestamp and a counter. So the entryCSN:s 
> are unique.
>
> But, the problem remains and I have no idea why this happens.
> I somehow still suspect that the problem still is in the initial
> phase of the sync operation (refresh stage). It might be that,
> some of the not-yet committed modifications don't make it into
> the result set in the search operation. Later after another entry
> is added, the "lost" entries are never to be synced over.

This also cannot be the cause. The contextCSN is snapshotted at the beginning of a 
refresh. Only updates between the consumer's cookie CSN and the snapshot CSN are 
sent to the consumer. Any entries added during this refresh will be excluded from 
the update, and the consumer will then record the snapshot CSN. Any entries the 
consumer didn't pick up in this refresh pass will be picked up in the next refresh.

> I will test some more and try to provide more information. I have
> a test program that generates this problem but it is a little
> cumbersome. I will try to slim it down and use more common schema
> elements before posting it.

That will certainly help.
--
  -- 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/