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

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

Testing again 'subordinate' looks irrelevant. I wonder what I
did in my original and bigger testcase to make it seem relevant.

On 1/19/19 6:30 PM, Howard Chu wrote:
> This is not really surprising.

I don't know these interactions well enough to be unsurprised.

It's not hard to guess that modify(olcDbIndex) might be heavy and
had better be tested.  A simple test says it returns quickly.  I
don't know why the ongoing indexing keeps cn=config locked after
the operation succeeded, instead of keeping something in the
indexed DB locked.  I wouldn't expect others to guess that either.

> Are you suggesting the indexing task should stop if another config mod comes in?

I'm suggesting to fail the 2nd operation if that's what it takes.
Or only hang if the user passes some LDAP control.

I'm suggesting that config pauses should be brief.  Server hangs
are bad.  Even a crash can be better when other load-balanced
servers can take over.  Not that I'm suggesting that "fix":-)