Issue 4254 - back-hdb deadlock under load
Summary: back-hdb deadlock under load
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-08 19:55 UTC by gael.roualland@oleane.net
Modified: 2014-08-01 21:06 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description gael.roualland@oleane.net 2005-12-08 19:55:14 UTC
Full_Name: Ga�l Roualland
Version: 2.3.13
OS: Linux
URL: ftp://ftp.openldap.org/incoming/gael-roualland-051208.log
Submission from: (NULL) (213.56.0.199)


Hello,

While benchmarking back-hdb on a large test directory running OpenLDAP 2.3.13,
after a while all threads stop responding and the slapd process comes to a
deadlock.
 
For the purpose of this bug report, I ran the test with slapd configured to run
with only 4 threads, and I have attached to the locked threads with gdb.
Relevant parts of the gdb session are in the uploaded file.

As you can see, the 4 worker threads are competing for the lru mutex and cache
rwlock. It looks like :
- thread 6 wants to lock the lru mutex at cache.c:442, while it has the rwlock
locked from cache.c:419
- thread 7 wants to lock the rwlock at cache.c:602, while it has the lru mutex
locked from cache.c:823

Thanks,

Ga�l.

Comment 1 Howard Chu 2005-12-08 22:24:19 UTC
Thanks for the report. I'd been looking into this for a while now, been 
testing a fix here. Should be ready soon.

gael.roualland@oleane.net wrote:
> Full_Name: Gaël Roualland
> Version: 2.3.13
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/gael-roualland-051208.log
> Submission from: (NULL) (213.56.0.199)
>
>
> Hello,
>
> While benchmarking back-hdb on a large test directory running OpenLDAP 2.3.13,
> after a while all threads stop responding and the slapd process comes to a
> deadlock.
>  
> For the purpose of this bug report, I ran the test with slapd configured to run
> with only 4 threads, and I have attached to the locked threads with gdb.
> Relevant parts of the gdb session are in the uploaded file.
>
> As you can see, the 4 worker threads are competing for the lru mutex and cache
> rwlock. It looks like :
> - thread 6 wants to lock the lru mutex at cache.c:442, while it has the rwlock
> locked from cache.c:419
> - thread 7 wants to lock the rwlock at cache.c:602, while it has the lru mutex
> locked from cache.c:823
>
> Thanks,
>
> Gaël.
>
>
>   


-- 
  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc
  OpenLDAP Core Team            http://www.openldap.org/project/

Comment 2 Howard Chu 2005-12-08 23:21:31 UTC
changed notes
changed state Open to Test
moved from Incoming to Software Bugs
Comment 3 Kurt Zeilenga 2005-12-21 20:49:19 UTC
changed notes
changed state Test to Release
Comment 4 Kurt Zeilenga 2005-12-23 22:30:00 UTC
changed state Release to Closed
Comment 5 Howard Chu 2009-02-17 05:17:20 UTC
moved from Software Bugs to Archive.Software Bugs
Comment 6 OpenLDAP project 2014-08-01 21:06:41 UTC
fixed in HEAD/re23