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.
Bug 785898 - Enable midway cache refresh by default
Summary: Enable midway cache refresh by default
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Stephen Gallagher
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-30 20:54 UTC by Stephen Gallagher
Modified: 2020-05-02 16:21 UTC (History)
4 users (show)

Fixed In Version: sssd-1.8.0-2.el6.beta2
Doc Type: Bug Fix
Doc Text:
Cause: For many releases, SSSD has had a performance option to enable updating of often-requested cache entries before their expiration in order to avoid cache-misses (and the wait time while the network communication occurs). This option was always disabled by default. Consequence: The default operation of SSSD's cache was not as efficient as it could be. Change: SSSD will now default to enabling the midway cache. Result: Users should see a significant reduction in cache-misses with SSSD, resulting in fewer interruptions in their workflow.
Clone Of:
Environment:
Last Closed: 2012-06-20 11:54:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 1960 0 None None None 2020-05-02 16:21:28 UTC
Red Hat Product Errata RHBA-2012:0747 0 normal SHIPPED_LIVE sssd bug fix and enhancement update 2012-06-19 19:31:43 UTC

Description Stephen Gallagher 2012-01-30 20:54:05 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/918

SSSD has a cache update feature that can renew the cache prior to expiration to reduce the cache-miss penalty on oft-requested entries. We originally opted to leave it disabled by default (since it increases load slightly on the LDAP server).

However, I think the performance gains on the client side are well-worth the small load increase on the server side (which would still be much lower than the load without SSSD at all).

I propose that we should change the default value for {{{entry_cache_nowait_percentage}}} to be 50% (so entries would automatically refresh out-of-band when they were queried after half of their expiration time has passed).
Comment 1 Jenny Severance 2012-01-31 14:58:48 UTC 
Please add steps to reproduce/verify this issue
Comment 2 Stephen Gallagher 2012-01-31 18:10:46 UTC 
Steps to reproduce:

1. Set entry_cache_timeout = 10. Leave entry_cache_nowait_percentage unset (at defaults).
2. Run 'time getent passwd <legitimate_user>' fifteen times, with a one-second sleep.

Results prior to this change:
The first request would go to LDAP and wait for the reply (can be detected by longer result from 'time') and then would go back to LDAP again after ten seconds, resulting in a delay on the eleventh lookup.

After this change:
Only the first request will wait on an LDAP lookup. After that, if the requests are coming in consistently, the lookup will be able to return from cache immediately.
Comment 3 Stephen Gallagher 2012-01-31 18:11:51 UTC 
Addendum: this concerns default behavior when entry_cache_nowait_percentage is unspecified. Previous versions of SSSD in RHEL would have been able to achieve this functionality by manually setting the entry_cache_nowait_percentage option to 50. This patch simply makes that value the default.
Comment 6 Amith 2012-05-02 22:09:16 UTC 
Verified on sssd-1.8.0-22.el6.x86_64.
Comment 8 Stephen Gallagher 2012-06-12 13:30:00 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: For many releases, SSSD has had a performance option to enable updating of often-requested cache entries before their expiration in order to avoid cache-misses (and the wait time while the network communication occurs). This option was always disabled by default.

Consequence: The default operation of SSSD's cache was not as efficient as it could be.

Change: SSSD will now default to enabling the midway cache.

Result: Users should see a significant reduction in cache-misses with SSSD, resulting in fewer interruptions in their workflow.
Comment 10 errata-xmlrpc 2012-06-20 11:54:32 UTC 
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-2012-0747.html
Note You need to log in before you can comment on or make changes to this bug.