[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: (ITS#8958) 2nd cn=config update blocks slapd while adding subordinate index
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#8958) 2nd cn=config update blocks slapd while adding subordinate index
- From: hyc@symas.com
- Date: Sun, 20 Jan 2019 04:27:09 +0000
- Auto-submitted: auto-generated (OpenLDAP-ITS)
Hallvard Breien Furuseth wrote:
> On 1/20/19 4:48 AM, Hallvard Breien Furuseth wrote:
>> On 1/20/19 2:14 AM, Howard Chu wrote:
>>> This was the safest approach, considering that a config change could alter/remove context out
>>> from under running threads otherwise.
>>
>> No, the safest approach is to fail the 2nd cn=config mod
>> unless the user says it's OK to block the server.
How would the user say so?
> Or fail the 1st cn=config mod too, if that's easier.
Huh? That op has already completed. The indexer is started as a background task after
the mod op completes.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/