[Date Prev][Date Next]
Re: syncrepl questions
--On Wednesday, September 24, 2003 11:23 AM -0700 "Kurt D. Zeilenga"
Actually, its not a "full" reload, but a update+present refresh
that will be common event. They occurs only during refresh and
then only when something has changed. So, avoid refresh (use
persist mode) and keep the retry interval short (to reduce the
chance something changes while disconnected).
As Jong noted, history information is needed to use the
updates+delete mode (except when there are no deletes, context
CSNs can detect that). That should make syncrepl good enough
for *most* directory deployments. Syncrepl, even with optimal
selection of transfer mode, is likely not good enough for larger
directories and/or frequently updated directories. For this,
one needs a protocol which transfers attribute level (or even
value-level) changes. Syncrel transfers entry-level changes.
I've changed back to persist mode, which is where I started at. If
syncrepl is not suited to large scale deployments/deployments with frequent
updates, does this mean the various ITS's against slurpd will be dropped
back into the queue to be fixed, instead of suspended?
Principal Software Developer
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html