[Date Prev][Date Next]
OpenLdap DB size difference after slapcat and slapadd.
- To: openldap-software@OpenLDAP.org
- Subject: OpenLdap DB size difference after slapcat and slapadd.
- From: Tech Guy <firstname.lastname@example.org>
- Date: Wed, 5 Jul 2006 07:49:33 -0700 (PDT)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Ow7b9JueRhRVSa05tBeAc62syHsvO5dRAESoeziMVXLh2xM0iSr3LwePI6GTj1Rawuli7HXSwfoeZ8oBIsnrzXbvGWAlQlK1OUku2EWrPfbvoO94E9PkqtU3F27cpBsOnecIhQF9QWc0ClFOIhBUWhXTBLbba8fU4Ru8CweRNPk= ;
We recently ran into the OpenLDAP(v2.1.12) index
corruption issue on a production system. I understand
that there is a fix for this in later versions and we
are in the process of upgrading our systems.
My question was related to the back-end database size
reduction we saw as a result of the steps we took to
recover from the issue.
Slapcat the database to an LDIF file
SlapAdd'ed the database back.
We noticed a reduction of size of ~200Mb and the ldbm
directory changed from 1000Mb to 800Mb after the
Approximate distribution of size changes
id2entry.dbb - Reduction of 163Mb
dn2id.dbb - Reduction of 54Mb
index dbb - Reduction of 11 Mb
My only explanation was the database storage was
fragmented before the slapcat and the slapadd resulted
in an optimized storing of records.
Can someone explain the reduction in size? Also, is
the slapcat and slapadd a recommended maintenance
practice to improve performance in OpenLDAP?
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around