Re: How correctly convert ldif dump size to mdb olcDbMaxSize value

[Quanah Gibson-Mount <quanah@symas.com>]

--On Tuesday, February 28, 2017 2:48 PM +0300 Ikonta <ikonta@yandex.ru> 
wrote:

> Hi everybody,
>
> I use simple OpenLDAP installation (two servers in mirror mode, something
> above 30000 leafs tree). Some time ago I've migrated it to mdb backend.
>
> The database dump in ldif weight about 300M.
> Initially I've set olcDbMaxSize to 2147483648 bytes (2G).
> Imported into directory it became about 450M data.mdb on node1 and after
> mirror synced — 1.5G replicated data.mdb on node2. Why instances
> database sizes are so different?
>
> Am I right guessing olcDbMaxSize is maximum size of data.mdb file?
> And how should I, starting with present and perspective ldif dump size,
> count proper value of olcDbMaxSize? For example, if I expect ldif dump
> may grow up to 500 M?

Generally, you just set it to something *very large*.  I usually go with 
80GB.  You're not supposed to try and keep it down to a small value that's 
"near" the actual DB size.

--Quanah


--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>