Bug 1215187

Summary:	timeout/expiry of group-cache should be set to 300 seconds
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	core	Assignee:	Niels de Vos <ndevos>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	mainline	CC:	bugs, gluster-bugs
Target Milestone:	---	Keywords:	EasyFix, Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://lists.fedorahosted.org/pipermail/sssd-devel/2014-November/021451.html
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1215189 (view as bug list)		Environment:
Last Closed:	2016-06-16 12:55:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1215189

Description Niels de Vos 2015-04-24 14:02:41 UTC

Description of problem:
The current timeout/expiry of the group-cache on the bricks is set to 5 (?) seconds. When sssd is used to request all the groups of a user, and the request requires network access (i.e. LDAP), expiry of the cache can happen way too often.

sssd has a default of 300 seconds for memory caching (groups are only cached on disk as of current sssd versions). Gluster should use the same timeout for caching, making it more sssd friendly and preventing high cpu usage in some environments where fetching groups is slow.

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

How reproducible:
100%

Steps to Reproduce:
1. have a user in many (100's of groups) in an LDAP structure
2. enable server-side group fetching with server.manage-gids=on for the volume
3. do some I/O as the user
4. see the slowness when groups need to be refreshed constantly

Actual results:
Gluster performs poorly.

Expected results:
The number of groups that a user belongs to should not affect performance *that* much.

Additional info:
https://lists.fedorahosted.org/pipermail/sssd-devel/2014-November/021451.html

Comment 1 Anand Avati 2015-04-24 15:09:39 UTC

REVIEW: http://review.gluster.org/10371 (protocol: increase default group-cache-timeout to 300 seconds) posted (#1) for review on master by Niels de Vos (ndevos)

Comment 2 Nagaprasad Sathyanarayana 2015-10-25 14:53:42 UTC

Fix for this bug is already made in a GlusterFS release. The cloned BZ has details of the fix and the release. Hence closing this mainline BZ.

Comment 3 Nagaprasad Sathyanarayana 2015-10-25 14:54:23 UTC

Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 4 Niels de Vos 2016-06-16 12:55:58 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user