Ondřej, I'm aware that doing the initial sync via accesslog is not the best idea, but first I wanted to check whether it works at all, and it also seems to be a good indicator whether the size of the databases is large enough (I'm new to mdb, and unfortunately SLES does not ship the mdb tools with OpenLDAP). And I'm using 11 equality only indices.
Mit freundlichen Grüßen Ulrich Windl > -----Original Message----- > From: Ondřej Kuzník <[email protected]> > Sent: Monday, March 17, 2025 1:29 PM > To: Windl, Ulrich <[email protected]> > Cc: Quanah Gibson-Mount <[email protected]>; openldap- > [email protected] > Subject: [EXT] Re: Re: accesslog seemingly needs a lot of space > > On Mon, Mar 17, 2025 at 08:44:55AM +0000, Windl, Ulrich wrote: > > Hi! > > > > Why should the number of entries in (size of) the main database not be > > correlated with the size of the accesslog regarding the initial sync? > > The more entrties in the main DB, the more entires in the accesslog, I > > guess. > > Hi Ulrich, > the size of an accesslog entry has to be considerably larger than the > size of the original entry, for starters it has to communicate a lot of > additional information/metadata about the operation. And that's assuming > you only enabled accesslog to log the bare minimum needed for > delta-syncrepl use. > > If you enabled any more (e.g. logsuccess false), enabling accesslog and > doing a live bootstrap would never strike me as a good combination. In > that case I would either slapadd from a recent backup or configure > accesslog afterwards. > > > As a matter of fact I suspect the unexpected size of my accesslog is > > due to the number of indices being configured (I have configured a few > > more than absolutely required). > > Unless you created any substring indexes or went really overboard, I > doubt it should cost that much. > > Regards, > > -- > Ondřej Kuzník > Senior Software Engineer > Symas Corporation http://www.symas.com > Packaged, certified, and supported LDAP solutions powered by OpenLDAP
