Learn more about these different git repos.
Other Git URLs
We found out that we didn't free a memory context where we should, which resulted in memory growth if the application requesting netgroups was a long-running one.
1) Run a process that requests a netgroup periodically but doesn't exit between the attempts. Maybe a deamon, python interpreter might do as well.
2) Watch the sssd_nss memory footprint grow
owner: somebody => lslebodn
priority: major => critical
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1038098 (Red Hat Enterprise Linux 6)
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1038098 1038098]
patch: 0 => 1
status: new => assigned
milestone: NEEDS_TRIAGE => SSSD 1.11.3
resolution: => fixed
status: assigned => closed
changelog: => The SSSD did not free per-client allocated memory when netgroups were requested. As a consequence, if netgroups were used by a long-running application, the sssd_nss process grew large in memory consumption.
Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.11.3
SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
to comment on this ticket.