[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Should Berkeley DB backends be reloaded occasionally?
- To: openldap-technical@openldap.org
- Subject: Should Berkeley DB backends be reloaded occasionally?
- From: Mark <mah042@gmail.com>
- Date: Tue, 31 May 2011 16:49:42 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=T8Eu9fn/H1iYDBDXi/oKxe6IEIy3ow4Ii6g0tD9BXhE=; b=Myj3Jot0QOuzv+FF3kgjWXatapWlU4t6Ymgz2kQMeGF53Xt0g5z7lykug+njLjo+X5 rXMwqy05QVLNeiLgW56tVfMUuI7ljdhUmZBzbY5lG0qpiUSFJKQ8te44BMVy9O5QcrhT Tzlb/P3ffitzJUpW5eYZ9k3qOTKcPnOZxt3CU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=YgXupaHSASwZGrgeRYwplzBg1iroISMRtFRqJ8Kj/B2KONMKwY6CkQ7cTXCZGTAxbK E/99HuLPF5ajCHrxrlzShckCDDHu+qu34MSTuUW1AucHZTe6GwBE1ABYMQ78YA0G3swE hbe39fyAM+5mo3BPFQHQ0HDDNVtgNgGkj09l4=
Back in the days of OpenLDAP 2.1 with Berkeley DB 4.1.25.3 we used to have to 'reload' out backend database occasionally as non-indexed reads would get slower and slower over time. The 'reload' entailed:
- stop slapd
- slapcat the contents to an .ldif file
- remove the database files
- slapadd the .ldif file to create a new, fresh db instance
- start slapd
Then our performance problems went away. Re-indexing didn't do the trick.
Is such occasional re-building of the backend database recommended in OpenLDAP 2.4.25 with Berkeley DB 4.8.30?
Thank you,
Mark