[jira] [Created] (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.

["Andrew Onischuk (JIRA)" <ji...@apache.org>]

Andrew Onischuk created AMBARI-12871:
----------------------------------------

             Summary: 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.
                 Key: AMBARI-12871
                 URL: https://issues.apache.org/jira/browse/AMBARI-12871
             Project: Ambari
          Issue Type: Bug
            Reporter: Andrew Onischuk
            Assignee: Andrew Onischuk
             Fix For: 2.1.2


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.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)