[Date Prev][Date Next]
RE: Running out of locks while building db
> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Kurt D.
> At 12:27 PM 2002-07-30, email@example.com wrote:
> >Configuring additional locks and lock objects (1800 of each)
> >seems to get me a little farther. Now it's reporting that it's
> >running out of memory. Any ideas?
> On some platforms, slapadd(8) appears to be leaking some
> resources. A couple ITSs have been filed. We haven't
> found the bug yet... workaround is to split your LDIF
> into smaller chunks.
There is also a bug in the 2.1.3 back-bdb/idl.c which can cause it to
return this "no space" error whenever an index slot hits about 65535 IDs.
This bug is fixed in the HEAD.
The whole issue of locks and lock objects is a little suspicious, unless
indexing a very large number of attributes. Otherwise, since slapadd is
single-threaded, there really shouldn't be many simultaneously held locks.
> >=> bdb_tool_entry_put( -1, "cn=nre301-003,ou=User
> >du" )
> >=> bdb_dn2id_add( "cn=nre301-003,ou=user
> groups,ou=groups,dc=umich,dc=edu", 0x00
> >010005 )
> >=> bdb_idl_insert_key: c_get last failed: Not enough space (12)
> >=> bdb_dn2id_add: subtree (ou=groups,dc=umich,dc=edu) insert failed: 12
> ><= bdb_dn2id_add: 12
> >=> bdb_tool_entry_put: dn2id_add failed: Not enough space (12)
> >=> bdb_tool_entry_put: txn_aborted! Not enough space (12)
> >slapadd: could not add entry dn="cn=nre301-003,ou=User
> >,dc=edu" (line=2096986): txn_aborted! Not enough space (12)
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
Symas: Premier OpenSource Development and Support