#3496 [RFE] Add a configuration option to SSSD to disable the memory cache
Closed: Fixed 2 years ago Opened 2 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1484376

Description of problem:
The ask here is to add a configuration option to tell the SSSD NSS responder to
not create the memory cache when the option is set.

We have seen issues with disk space in environments where sssd is restarted in
short intervals. It's clear that disabling the memory cache will have a
negative impact on NSS performance, but in some situations it might be helpful
to have such an option available.

Setting the "SSS_NSS_USE_MEMCACHE" env variable to "no" does not always help
because some services clear their environment before starting the actual
process. In this case the env variable is unset and the service is still using
the memory cache even though it has been told to not use it.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1484376

2 years ago

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1484376

2 years ago

Metadata Update from @mzidek:
- Issue assigned to mzidek

2 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.0

2 years ago

Metadata Update from @jhrozek:
- Issue priority set to: blocker
- Issue tagged with: PR, RFE

2 years ago

Just for the record, Today (Oct 19th 2017) there was a phone meeting between the SSSD core developers and we agreed, by majority, on having a extended version of https://github.com/SSSD/sssd/pull/390#issuecomment-334434651 (provided by @lslebodn) pushed to our git master.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)

2 years ago

Metadata Update from @jhrozek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata