[AMBARI-12871] Ambari startup scripts exhibit long delays (5+ seconds each) on every "modifying user" operation. This adds a few minutes to the time it takes to start or restart any component, causing excessive downtime for every config change.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.2
• Assignee: Andrew Onischuk
• Reporter: Andrew Onischuk
• Created: 25/Aug/15 12:19
• Updated: 26/Aug/15 11:20
• Resolved: 26/Aug/15 09:31

Description

PROBLEM: Customer use nslcd to fetch the user from AD server, it returns a lot
of users and groups, this will slow down the ambari operation (start/stop
service). As discussed with Florian Barca, The root cause is a limitation in
the native API: grp.getgrall() has no ability to prefilter the results, which
means it fetches all users from the LDAP directory exposed by nslcd. If it
happen to be a large org, with a large number of users, so the fetch takes a
long time. We need to optimize this and make the code scale with the number of
users.

Issue Links

• links to: ReviewBoard