[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: back-bdb future

The recent index DB subdatabase patch of Howard
seems to solve the deadlock problem ! (dbcache.c version 1.25)
I experimented with 200K entries and the test run went well.
I'll try a million entry run during the weekend.
BTW, it does not seem to be related to the pthread mutex,
because the deadlock occurred even when the number of threads is set to
just 1.
- Jong

Jong Hyuk Choi
IBM Thomas J. Watson Research Center - Enterprise Linux Group
P. O. Box 218, Yorktown Heights, NY 10598
email: jongchoi@us.ibm.com
(phone) 914-945-3979    (fax) 914-945-4425   TL: 862-3979

"Howard Chu" <hyc@highlandsun.com> on 03/28/2003 10:30:04 PM

To:    Jonghyuk Choi/Watson/IBM@IBMUS
cc:    "'Kurt D. Zeilenga'" <Kurt@OpenLDAP.org>,
Subject:    RE: back-bdb future

Ah, now I see. The dbcache code uses its own mutex to protect the list of
open databases. Since this lock is outside the BDB system, the deadlock is
not detected. I think using a DB lock here will take care of the problem.

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