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

Re: Antw: Re: Denying access to syncrepl consumere during initial DIT content load

Ulrich Windl wrote:

Hi!

Stupid question: If syn is based on entryUUID and entryCSN and objects are
transferred in transactions, how can an obsolete or incomplete object exist on
a server that is to be synced?
There cannot be incomplete individual entries. There can of course be incomplete collections of entries. And since refreshes occur in arbitrary order, you may have children objects replicated before their parents.
For a large refresh, an entry may be replicated that gets changed again on the provider while the refresh is in progress, and so the version on the consumer is already out of date/obsolete. 


Regards,
Ulrich


Michael StrÃder<michael@stroeder.com> schrieb am 24.03.2014 um 12:03 in

Nachricht <53301109.9070703@stroeder.com>:

Emmanuel Dreyfus wrote:

On Mon, Mar 24, 2014 at 10:11:40AM +0100, Christian Kratzer wrote:

This is another situation in which it would be nice to be able to

disallow

any ldap connections to a consumere while it is in the initial sync

phase.


Any client should be denied during this phase: you do not want to serve
incorrect information.

I have slapd startup script that run slapd on an alternate port until
replication is in sync, then starts normally.


How do you detect that replication is in sync?
Do you look at the contextCSN attribute?

Ciao, Michael.







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