[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
delta sync and strictrefresh
- To: openldap-technical@openldap.org
- Subject: delta sync and strictrefresh
- From: "A. Schulze" <sca@andreasschulze.de>
- Date: Tue, 08 Mar 2016 21:13:16 +0100
- Content-disposition: inline
- Dkim-filter: OpenDKIM Filter v2.11.0 mail.somaf.de 3qKSQl49VlzDgv
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=andreasschulze.de; s=ybz; t=1457467999; bh=4el7FCEHjb8QGgjrEqwwdXmF6h8seS+2KXyJ1NjReak=; h=Date:From:To:Subject; b=gcte3OUrj44GbVf15Yop9MEo8W/zGEvguRz/D2n/bHjRAieGe+rKkled+em82uQ9t zxVLOeEWx01+39LwFWmF5fw5VvO7H2owfMjfZ7/nBOVJQDipJ5TGB2DmNt35OeoBtR OaExTTKD4aPzkHzJZAAQhsOL3/hK03e0iO9UZmptiVGFpSPfSz2CFdKJQtm9GOT25o 6DwsqHXEfQB90bdN7cryTChrJelx0LZ+MFGL35Wr88FM7KemuBIEsUB+Tq+8LiYm5d HdTQECbBY+HumpknFnMXDmM9oIzFkKawJTUdPWap/B4FNsccdJde13EKhq5ckt9MK6 +SgAXyfvoKz5w==
- User-agent: Horde Application Framework 5
Hello,
I'm a longtime openldap and syncreplica user. Now I learned about
delta replication and the option "strictrefresh".
But it doesn't work as promised. Maybe my expectation is simply wrong...
Let's describe my use case:
One ore two provider serve data to numerous consumer.
Application running on the consumer host are configured to query the
local consumer first
and fall back to the provider. A typical LDAP-URI looks like
"ldap://localhost ldaps://provider1 ldaps://provider2"
Application only /read/ data.
Sometimes it happen the consumer go out of sync. Convenient solution:
delete the consumer ldap database and restart slapd. Now it take some
time to fetch the whole data from provider to consumer server.
Just in this time frame the application may query ldap://localhost and
get an answer which is simply wrong
because the data transfer is still in progress. That's what I want to avoid.
Is that possible with openldap at all
Thanks,
Andreas