[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: Sat, 19 Jan 2019 17:30:31 +0000
- Auto-submitted: auto-generated (OpenLDAP-ITS)
h.b.furuseth@usit.uio.no wrote:
> Full_Name: Hallvard Breien Furuseth
> Version: 2.4.47, master
> OS: Linux x86_64
> URL: ftp://ftp.openldap.org/incoming/Hallvard-Furuseth-190119.tgz
> Submission from: (NULL) (193.90.50.50)
>
>
> Use cn=config to add an index to a subordinate database,
> then make a 2nd cn=config change. 2nd change waits while
> (I assume) indexing, and blocks other slapd operations.
> So ldapwhoami during 2nd change takes 5 seconds.
>
> To reproduce: ./bug.sh
> To debug, attach gdb in another terminal during 2nd MOD.
> gdb -q ../servers/slapd/slapd `cat slapd.pid`
>
> trace.txt shows the 2nd config_back_modify() waiting
> in slap_pause_server().
This is not really surprising. Are you suggesting the indexing task should stop if another config mod comes in?
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/