RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47693

Environment variables (except TERM and LANG) are ignored if a program is started via service.

If it is started with systemctl, it takes this COMMAND and the values are correctly passed to the server.
systemctl set-environment SLAPD_MXFAST=0 MALLOC_TRIM_THRESHOLD_=4096

But to control them explicitly and to provide the same instructions to the service and systemctl, it'd be good to have some variables (proposing SLAPD_MXFAST, MALLOC_TRIM_THRESHOLD_, and MALLOC_MMAP_THRESHOLD_) configurable.

Steps to Reproduce:
1. setup 2 way mmr
2. add then delete 1 million entries
3. add 250000 entries

Set these config parameters in cn=config
nsslapd-malloc-mxfast: 0
nsslapd-malloc-trim-threshold: 4069
nsslapd-malloc-mmap-threshold: 33554432

Restart the server.

Repeat these searches for 1 hour.
ldapsearch 'objectclass=nsTombstone'
ldapsearch 'objectclass=*'

If the server's process size is sane, the fix is verified.

*** Bug 1111403 has been marked as a duplicate of this bug. ***

There are memory leaks reported from reliab15 execution So, this issue can be resolved only when this bug is fixed - Bug #1138745.

Recent reliab15 execution against build 1.2.11.15-45 running fine. No issues reported from the execution. Hence, marking the bug as Verified as Sanity only.

Beaker job - https://beaker.engineering.redhat.com/jobs/749819

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1385.html