Hi, On Thu, Mar 26, 2015 at 01:50:27PM +0300, Sergey Esin wrote:
Hi all, We're running OpenLDAP 2.4.40 (the latest available release) with just one replica server (connected via TLS) and have the following picture - http://i.imgur.com/om0lMiy.png On the graph you can see memory consumption of the slapd process on the host: in the beginngin it started without replica, then replica server was connected (memory consumption became around 4 Gigs) and then OOM (out-of-memory) killer on linux machine just killed the process.
I've seen a similar thing recently. The test case I posted to ITS#8081 causes very high memory usage on the host. (The crash bug is unrelated, it was a regression introduced after 2.4.40 was released.) Are you able to share your host config for comparison?
Howard wrote https://github.com/hyc/mleak while looking into it, but AFAIK we don't have a proven cause, only a suspicion that memory fragmentation may be involved.
Do your logs show what kind of client activity triggered the growth? Do you use delta-syncrepl?
There are ~400 000 users in our ldap database. OpenLDAP was compiled from sources using "./configure --prefix=/ldap2440 --with-tls --enable-slapd". Are there any ways to understand what's is going wrong and how to fix it? This server is really important for us, please share any ideas how to make it stable! My DB_CONFIG is like below: set_flags DB_LOG_AUTOREMOVE set_cachesize 0 524288000 5 set_lg_regionmax 1048576 set_lg_max 10485760 set_lg_bsize 2097512 set_lk_max_locks 23000 set_lk_max_lockers 2300 set_lk_max_objects 2300 -- Regards, Sergey
Attachment:
signature.asc
Description: Digital signature