[Date Prev][Date Next]
Re: (ITS#5860) slapd memeory leak under openldap 2.4
--On Wednesday, January 21, 2009 12:23 PM -0800 Rodrigo Costa
> My initial attempt was using openldap2.4.11 since this is the stable
> version. At this version Berkeley DB 4.7 isn't supported and then I used
> the BDB 4.6 with all patches.
I hardly consider 2.4.11 stable, regardless of what the tag is. I would
advise trying something more current (such as 2.4.13). And with BDB 4.7 +
> At this configuration, having the DB_CONFIG setup for 50MB, and even
> having the idlcache and cache sizes defined I continue to see the memory
> being allocated and never released by slapd.
What about dncachesize as well?
> 2.3.27-8.el5_2.4 where the CentOS5.4 uses a built-in backend library for
If you are looking for stability, I would hardly go with the crappy release
CentOS ships. The final 2.3 release was 2.3.43. Use it instead if you
want to use 2.3.
Also, are you on a 32 or 64-bit system? I certainly have no problems going
over 3GB on my 64-bit systems.
[zimbra@ldap openldap-data]$ du -c -h *.bdb
DB is 13GB in size.
[zimbra@ldap openldap-data]$ cat DB_CONFIG
set_cachesize 8 0 2
8447 zimbra 17 0 9.9g 8.9g 8.1g S 34 57.5 39:20.57 slapd
Using OpenLDAP 2.3.42.
Principal Software Engineer
Zimbra :: the leader in open source messaging and collaboration