On Tue, 2008-01-15 at 10:46 -0800, Quanah Gibson-Mount wrote: > --On Tuesday, January 15, 2008 12:02 PM -0600 Pat Riehecky > <[EMAIL PROTECTED]> wrote: > > > I would like to add my $0.02 to have this feature added, it would almost > > certainly come in hand when bug #333428 is completed. > > > >> From an admin perspective, I wouldn't mind a nice easy no brainer way to > > fire off an ldap reindex when I think it is necessary. > > If you use back-config in OpenLDAP 2.4 to control your configuration, if > you change the indices, it automatically kicks off a background thread to > update them. >
Right then, Any ideas when 2.4 is coming for debian? Will it use back-config by default? If not, a way of duplicating the behavior via slapd.conf would be very very handy.... > > I would like to add my $0.02 to have this feature added, it would > > almost > > certainly come in hand when bug #333428 is completed. > > Out of curiosity, why would one want to re-index at startup of slapd? > indices are maintained as data is modified. The only time one needs to > re-index is if they have modified their indices. In OpenLDAP 2.4, it is > trivial to re-index just those attributes that you've modified the indices > for, by passing them to slapindex. This is far superior than attempting to > re-index the entire database, which could take quite a long time on large > databases. Start up seems reasonable simply because I/O should be very quiet then. It will take forever on large databases, but for replicated databases a phased reindex /could/ come in handy. I know at my site (a university) we do crazy bulk loads once a year (incoming freshman) and performance isn't so snappy until after a reindex. It might be my tunings, but with the re-index everything goes fine so my thinking is it is a few fragmented indexes.... Pat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
