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.

Description of problem:
Right after instance creation, ns-slapd consumes 500+ MB:

# ps -e -o vsz,rss,comm | grep ns-slapd 
1142692 571428 ns-slapd

Previously it was just 30+ MB:
# ps -e -o vsz,rss,comm | grep ns-slapd
1062684 32336 ns-slapd


Version-Release number of selected component (if applicable):
389-ds-base-1.4.2.4-6.module+el8.2.0+5509+885f7879.x86_64

How reproducible:
always

Steps to Reproduce:
1. dscreate create-template > template.inf
2. dscreate from-file template.inf
3. ps -e -o vsz,rss,comm | grep ns-slapd


Additional info:
The root cause seems to be related to systemd (possibly bz1789930)
With systemd-239-19.el8.x86_64
# systemctl show -p LimitNOFILE dirsrv@localhost
LimitNOFILE=4096

With systemd-239-21.el8.x86_64 and higher:
# systemctl show -p LimitNOFILE dirsrv@localhost
LimitNOFILE=1048576

Indeed, seems to be a bug in systemd:
# systemctl show -p LimitNOFILE dirsrv@localhost 
LimitNOFILE=4096
# systemctl daemon-reload 
# systemctl show -p LimitNOFILE dirsrv@localhost 
LimitNOFILE=1048576

Until systemd bug is fixed, we can reintroduce LimitNOFILE in our service file

I was wondering if the memory consumption was due to large connection table.
At the moment, I expect nsslapd-conntable to be set to a low value (something like 1024) so even if maxdescriptor bumped to 1M (because of systemd or #49990) I would not expect the table to be that large.
When it happens what are the values of nsslapd-conntable and nsslapd-maxdescriptor ?

Build tested: 389-ds-base-1.4.3.8-3.module+el8.3.0+6935+6f68b788.x86_64

# ps -e -o vsz,rss,comm | grep ns-slapd
565216 45380 ns-slapd

# systemctl show -p LimitNOFILE dirsrv@localhost
LimitNOFILE=262144

Marking as VERIFIED, SanityOnly.

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 (389-ds:1.4 bug fix and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2020:4695