If you are using standard syncrepl (rather than delta-syncrepl), I'm not
sure what you're reporting is out of the ordinary and is not indicative of
a memory link. This is also why the issue "resolves" when ldap2 is
stopped. I.e., the issue is related to how syncrepl functions and what it
stores in memory while the lagging consumer is pulling down the database.
I suggest switching to using delta-syncrepl and seeing if you see the same
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: