Bug 646329

Summary: taking a long time to get a result of getent group when the group has a large number of users
Product: Red Hat Enterprise Linux 5 Reporter: Masahiro Matsuya <mmatsuya>
Component: nss_ldapAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: Ondrej Moriš <omoris>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.5CC: dpal, jplans, omoris, rdassen
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: nss_ldap-253-39.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-21 08:03:37 UTC Type: ---
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: 590060    

Description Masahiro Matsuya 2010-10-25 07:40:44 UTC 
Description of problem:

A customer has some very large groups, and it takes a long time for their membership to be transferred via ldap which excessively delays our applications.

Their largest group takes almost three minutes to look up:

 rhel5 ~ # time getent group students
 students:*:1438:tester,[...]
 real    2m53.334s

This group has about 23000 users in it.

This can be fixed by a fix of http://bugzilla.padl.com/show_bug.cgi?id=293.
This added the nss_getgrent_skipmembers option, allowing group members not to be returned via ldap.

Actually, this customer confirmed the fix on their environment.


Version-Release number of selected component (if applicable):
nss_ldap-253-25

How reproducible:
Always

Steps to Reproduce:
1. configure the ldap server and ldap client
2. create a group with a large number of users. (In case of this customer, it's about 23000 users)
3. run getent
  
Actual results:
it takes a long time to get a result of getent group when the group has a large number of users.

Expected results:
getent group returns the result in a short time.
Comment 6 errata-xmlrpc 2011-07-21 08:03:37 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-1030.html