Bug 805930

Summary:	Change behavior of clients once shared memory cache is enabled
Product:	Red Hat Enterprise Linux 7	Reporter:	Dmitri Pal <dpal>
Component:	sssd	Assignee:	SSSD Maintainers <sssd-maint>
Status:	CLOSED UPSTREAM	QA Contact:	Namita Soman <nsoman>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	jgalipea, jhrozek
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-23 13:27:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.