Re: back-bdb IDL limitations

[Jonghyuk Choi <jongchoi@us.ibm.com>]

A transaction begins and commits on
a cluster boundary as well. If something bad happens in the middle of slapadding,
the database will remain intact up to the previous cluster commit. I don't
see this as a limitation as long as the administrator is given the information
on the point his/her slapadd progressed to and as long as the cluster size
is not too large.
- Jong-Hyuk

------------------------
Jong Hyuk Choi
IBM Thomas J. Watson Research Center - Enterprise Linux Group
P. O. Box 218, Yorktown Heights, NY 10598
email: jongchoi@us.ibm.com
(phone) 914-945-3979    (fax) 914-945-4425   TL: 862-3979

"David Boreham" <david_list@boreham.org> Sent by: owner-openldap-devel@OpenLDAP.org 03/04/2005 09:21 AM

To:        <openldap-devel@OpenLDAP.org>         cc:                 Subject:        Re: back-bdb IDL limitations

Instead of writing to the index database
upon addition of every single ID, slapadd can be made to buffer multiple
IDs to make an ID cluster and writes the cluster as a single unit.

Question: What happens if the process dies,
or the hardware shuts down in the middle of one of
these group commit operations ?

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature