Bug 805930 - Change behavior of clients once shared memory cache is enabled
Summary: Change behavior of clients once shared memory cache is enabled
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-22 13:40 UTC by Dmitri Pal
Modified: 2020-05-02 16:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-23 13:27:17 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 2240 0 None None None 2020-05-02 16:45:26 UTC

Description Dmitri Pal 2012-03-22 13:40:34 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1198

Right now we do not close the socket used to contact the responders from the clients. This is to avoid overheads when many operations are performed.

Once the shared memory cache is implemented the number of times we will need to contact the responders should be dramatically reduced, therefore we should try to close the socket after each operation. An exception could be enumerations, which spans multiple calls/operations.
Comment 3 Jakub Hrozek 2016-11-23 13:27:17 UTC 
We are keeping track of this requirement in SSSD upstream trac. But since this change was not needed in 4+ years and additionally until the memory cache supports more use-cases like by-SID requests which are tracked separately and lastly because there is not much to test from the QE side here, I'm closing this bug report with the resolution of UPSTREAM.

Please reopen this bugzilla if you disagree.
Note You need to log in before you can comment on or make changes to this bug.