Uploaded image for project: 'Ambari'
  1. Ambari
  2. 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.

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.2
    • Component/s: None
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                aonishuk Andrew Onischuk
                Reporter:
                aonishuk Andrew Onischuk
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: