[Date Prev][Date Next]
RE: back-bdb deadlocks
> -----Original Message-----
> From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
> At 09:52 PM 2002-01-16, Howard Chu wrote:
> >I still get locked up running the updated test script. Also the
> number of locks
> >in use keeps growing up. Looks like a lock leak. (Say that 5 times
> fast...) I'm
> >surprised you're not seeing the same thing.
> It ran all night here without a problem.
> I do have one problem, seems I cannot run db_ utilities concurrently
> with slapd and, if I do, slapd does hang. This may be a local
> configuration problem. I'm going to re-configure to remove that
> as a problem source and retest, hopefully later today.
I moved from my SuSE 6 system to a SuSE 7 platform, and it runs to completion,
although very very slowly. There are far too many conflicts, many more aborts
than commits. So I guess part of the problem is glibc 2.0.7 (on my SuSE 6
system) is too broken to handle this.
Also, on a distantly related topic, SuSE 7.0 includes glibc 2.1.3, which
provides the pthread_attr_setstacksize() function, but it ignores any values
over the hardcoded 2MB limit. (It takes the min() of the user-specified size
and the hardcoded limit.) This gets thread stack overruns in bdb_search, just
like glibc 2.0.7. I note that configure doesn't explicitly check for the
presence of the pthread_attr_setstacksize() function, I think we need a test
for its presence and for it to behave as desired. I haven't quite figured out a
simple test for the proper behavior.
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
Symas: Premier OpenSource Development and Support