On 06/15/2012 03:16 PM, hyc@symas.com wrote:

jsynacek@redhat.com wrote:

...

Full_Name: Jan Synacek Version: git (c73ec15) OS: linux-fedora17 URL: http://jsynacek.fedorapeople.org/openldap/leak/openldap-mmr-leak.tar.gz Submission from: (NULL) (209.132.186.34)

I'm using a 2-node mmr setup on my local machine - configuration files and 'uploader' scripts are provided in the archive.

1. I have the two nodes running.
2. Execute run.sh (only a wrapper for ldapusradm.sh) and start monitoring

slapd's memory usage. 3) After some time (at about 2k users on my system), slapd consumes a large amount of memory which is still growing

Note that not using ldapmodify to add members to 'cn=users,dc=yes,dc=my', but using it e.g. for modifying each user's email, does NOT result in any memory leakage.

I have also created a massif output using valgrind's massif tool: http://jsynacek.fedorapeople.org/openldap/leak/massif.out.17906

I found a very similar bug (#7292), but I'm not sure if it's related.

Running RE24 with valgrind --leak-check=full I see no leak when running your test. That should be the same as git c73ec15. No idea what leak you're seeing.

The memory consumption still grows and slapd eventually gets killed by oom-killer.

Also, the second node (the one that the data is being replicated to) constantly calls dnPretty and dnNormalize on every single user that it has synced. At about 2k users, this starts to really show on CPU usage and overall speed as well.