RE: back-bdb future

[Jonghyuk Choi <jongchoi@us.ibm.com>]

environement cache size was set to a very large value.

> -----Original Message-----
> From: owner-openldap-devel@OpenLDAP.org
> [mailto:owner-openldap-devel@OpenLDAP.org]On Behalf Of Jonghyuk Choi


> It seems that deadlock freedom is not guaranteed if a DB access
> is outside transaction when we use the BDB transactional store.
> The deadlock case in 8 way machine is somewhat strange.
> It was only search threads that were attempting to open the
> index database.
> If deadlock occurs among search threads, timeout for txns
> would not help.
> Any idea why only search threads reach deadlock ?
> Unless we use CDB, even search only case not free from deadlock ?
> - Jong

Unless there's a bug in BDB, the only reason for this to happen is if the
environment's memory size is too small, and there aren't enough free pages
to
satisfy all of the search threads at once. In that case, forcing one of the
readers to abort may resolve the situation, and so setting a timeout could
work. I'd be curious to see if db_stat showed you had hit any resource
limits
first.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support