Re: (ITS#8958) 2nd cn=config update blocks slapd while adding subordinate index

[h.b.furuseth@usit.uio.no]

On 1/19/19 8:04 PM, Howard Chu wrote:
> modifications to cn=config require no other threads to be active. Once the background indexer
> starts running, its activity will of course block further cn=config modifications until it
> completes.

Nothing "of course" about it.  I don't know why running
the background indexer is considered a change to cn=config.
The ldapmodify did the change to cn=config and completed.

I can guess that it might block cn=config simply because that's
the safe way to have both an indexer and dynamic config.  Or
I can read the code.  But "read the code" != "of course".

So... back to start, I guess I was suggesting that the
indexing task should stop if another config mod comes in,
if it can resume afterwards.  And the config change need
only fail if it might prevent the indexer from resuming.
I suppose that gets complicated in a hurry though.