Re: slapd hangs at 100% cpu in sched_yield (ITS#2030)

[Kurt@OpenLDAP.org]

At 10:02 PM 2002-08-20, steven.wilton@team.eftel.com wrote:
>On Wed, 21 Aug 2002 11:31:20 Kurt D. Zeilenga wrote:
>>Your suggestion will quite likely result in resource deadlock.
>>It will certainly spend huge amount of cycles unnecessarily
>>in a busy loop.  A loop which includes a back-off delay and
>>is finite might be acceptable.
>
>This does sound like the best solution.  I prefer the idea of returning LDAP_BUSY, as this error will only occur while the server is under load.

We've traditionally returned LDAP_OTHER on resource exhaustion
(thinking that the condition would likely not go away).  But
I'm fine with LDAP_BUSY (especially as we change the server
to better deal with resource exhaustion).

> Is it worth making some of these db options configuration
> file options, as people will probably have to play with them
> once they start using bdb4 database backends?

No.  See software/devel list discussions.