[Date Prev][Date Next]
Re: (ITS#5840) bdb_online_index and shutdown
> Am Mittwoch 03 Dezember 2008 04:10:36 schrieb firstname.lastname@example.org:
>> On Tue, Dec 02, 2008 at 03:14:28PM +0000, email@example.com wrote:
>>> Full_Name: Ralf Haferkamp
>>> Version: HEAD, RE24
>>> URL: ftp://ftp.openldap.org/incoming/
>>> Submission from: (NULL) (18.104.22.168)
>>> When slapd is shutdown while the online indexing task is active it will
>>> stop the indexing task immediately leaving a half created index files
>>> behind. Searches that use the index afterwards will return imcomplete
>>> I wonder if we should wait for the indexing task to complete when
>>> shutting down the daemon or if there are any other ways to put the
>>> databases and the configuration back into a consistant state. (Apart from
>>> manually running slapindex)
>> That's documented behavior. (See the Admin Guide:
>> If slapd is stopped before the index task completes, indexing
>> will have to be manually completed using the slapindex tool.
>> Generally when people issue a shutdown command to slapd they want it to
>> Stop Right Now. I think it would be a bad idea to wait, and I see nothing
>> to change here. This ITS should be closed.
> Ok, waiting for the index task to complete is a bad idea as it can take very
> long to complete. But could we indicate the condition somehow that warn the
> user about an incomplete run upon next startup?
- the index should be invalidated
- slapd, at the next manual startup, should complain about the need to
run slapindex first.
- in order to allow consistent batch restart with no human intervention,
slapd could allow to be restarted without running slapindex first, but
without making use of the inconsistent index.
my 2c, not volunteering right now.
Ing. Pierangelo Masarati
OpenLDAP Core Team
via Dossi, 8 - 27100 Pavia - ITALIA
Office: +39 02 23998309
Mobile: +39 333 4963172
Fax: +39 0382 476497