> -----Original Message----- > From: Quanah Gibson-Mount <[email protected]> > Sent: Monday, March 17, 2025 6:08 PM > To: Windl, Ulrich <[email protected]>; Ondřej Kuzník <[email protected]> > Cc: [email protected] > Subject: [EXT] RE: Re: Re: accesslog seemingly needs a lot of space > > > > --On Monday, March 17, 2025 3:17 PM +0000 "Windl, Ulrich" > <[email protected]> > wrote: > > > 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. > > Indices on the main DB have no correlation to the size of the accesslog DB, > which has its own set of required indices. The reason why the accesslog
[Windl, Ulrich] Of course those 11 indoces are on the accesslog database. > tends to be *larger* than the main DB is it records all change traffic (at > least with a minimum of just delta-syncrepl and/or session log). Now, if > you never have changes, or you have very few changes in your environment, > and you had a very large main database, then it's possible the accesslog DB > would be smaller than the main DB. Additionally, the accesslog is > generally configured to hold all changes over a span of time (I've > generally done 1-2 weeks). > > So the size of the accesslog DB is determined by a number of things: > > * What operations you specifically have logged into it (changes > (delta-syncrepl) or more) > * How long it's configured to keep those changes in the accesslog DB > * The rate at which recorded operations occur on your primary database [Windl, Ulrich] Thanks for explaining! > > --Quanah >
