[Bugs] [Bug 1215187] New: timeout/expiry of group-cache should be set to 300 seconds

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1215187

            Bug ID: 1215187
           Summary: timeout/expiry of group-cache should be set to 300
                    seconds
           Product: GlusterFS
           Version: mainline
         Component: core
          Keywords: EasyFix
          Assignee: bugs at gluster.org
          Reporter: ndevos at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.