Re: (ITS#4411) ldapsearch hangs with proxyCache

[hyc@symas.com]

Dave Horsfall wrote:
> On Thu, 23 Feb 2006, Howard Chu wrote:
>
>   
>> You're indexing a lot more attributes than you actually list in the 
>> proxytemplate. If attributes aren't used in a filter, there is no reason 
>> to index them.
>>     
>
> That's because those are the attributes I'll be using once I get the proxy 
> cache working; this is merely a test case.
>
>   
>> I note that the backtrace you sent shows BerkeleyDB stuck trying to 
>> acquire a lock in the cursor close function. The db_stat output you sent 
>> doesn't include your /var/tmp/AdminViewCache status though, so it 
>> provides nothing relevant to the current situation.
>>     
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Lock region parameters
> locker table size: 1031, object table size: 1031, obj_off: 360104,
> osynch_off: 0, locker_off: 351848, lsynch_off: 0, need_dd: 0
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Conflict matrix
> 0	0	0	0	0	0	0	0	0	
> 0	0	1	0	1	0	1	0	1	
> 0	1	1	1	1	1	1	1	1	
> 0	0	0	0	0	0	0	0	0	
> 0	1	1	0	0	0	0	1	1	
> 0	0	1	0	0	0	0	0	1	
> 0	1	1	0	0	0	0	1	1	
> 0	0	1	0	1	0	1	0	0	
> 0	1	1	0	1	1	1	0	1	
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Locks grouped by lockers
> Locker   Mode      Count Status  ----------------- Object ---------------
>        1 dd= 0 locks held 1    write locks 0      
>        1 READ          1 HELD    id2entry.bdb             handle        0
>
>        2 dd= 0 locks held 0    write locks 0      
>        3 dd= 0 locks held 1    write locks 0      
>        3 READ          1 HELD    dn2id.bdb                handle        0
>
>        4 dd= 0 locks held 0    write locks 0      
>        5 dd= 0 locks held 0    write locks 0      
>        6 dd= 0 locks held 0    write locks 0      
>        7 dd= 0 locks held 0    write locks 0      
> 80000006 dd= 0 locks held 1    write locks 0      
> 80000006 READ          1 HELD    dn2id.bdb                page          1
>
> 80000007 dd= 0 locks held 2    write locks 1      
> 80000007 READ       2655021 HELD    dn2id.bdb                page          1
> 80000007 WRITE      2655024 HELD    dn2id.bdb                page          1
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Locks grouped by object
> Locker   Mode      Count Status  ----------------- Object ---------------
> 80000006 READ          1 HELD    dn2id.bdb                page          1
> 80000007 WRITE      2655024 HELD    dn2id.bdb                page          1
> 80000007 READ       2655021 HELD    dn2id.bdb                page          1
>
>        1 READ          1 HELD    id2entry.bdb             handle        0
>
>        3 READ          1 HELD    dn2id.bdb                handle        0
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Memory free list
> 0x2823d004: 119836	
>
>   
Those lock counts are ridiculously high. What does db_stat -c say for 
this same directory? It seems you've run out of BDB lock resources, 
which can easily happen when you have a lot of indexing configured.

-- 
  -- 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/