[Date Prev][Date Next]
RE: ITS#1679 gentle SIGHUP handling
At 01:12 PM 2002-04-03, Howard Chu wrote:
>It occurs to me that entry caching could give you an old view of things but
>I wouldn't expect it to be a major issue, most sessions are pretty short
>lived as it is. For services that keep a single long-lived session open, it
>would be useful to give them some kind of indication that they ought to
>close and re-open the session. Not sure how that should work.
>It may be a good idea to have the frontend return UNWILLING_TO_PERFORM on
>all new update requests once a gentle shutdown has started.
LDAP_UNAVAILABLE would be more appropriate in this case.
>wouldn't address the problem of long-lived read-only sessions though...
> -- Howard Chu
> Chief Architect, Symas Corp. Director, Highland Sun
> http://www.symas.com http://highlandsun.com/hyc
> Symas: Premier OpenSource Development and Support
>> -----Original Message-----
>> From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
>> Sent: Wednesday, April 03, 2002 12:55 PM
>> To: Howard Chu
>> Cc: openldap-devel@OpenLDAP.org
>> Subject: Re: ITS#1679 gentle SIGHUP handling
>> At 12:19 PM 2002-04-03, Howard Chu wrote:
>> >This sounds like an extremely good feature for reconfig
>> restarts. Assuming
>> >that back-bdb allows multiple processes to access a single database, this
>> >should allow seamless restarts of slapd with no interruption of
>> service. Has
>> >anyone tried it?
>> It should be okay to read the database while slapd/back-bdb
>> is running. That is, you should be able to do a on-the-fly
>> backup. However, I haven't tried this yet.
>> However, you shouldn't write to the database while slapd/back-bdb
>> is running as slapd/back-bdb.