ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk" <>
Subject Re: Review Request 37758: 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.
Date Tue, 25 Aug 2015 14:48:36 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated Aug. 25, 2015, 2:48 p.m.)

Review request for Ambari, Dmitro Lisnichenko and Vitalyi Brodetskyi.

Bugs: AMBARI-12871

Repository: ambari


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

Diffs (updated)

  ambari-server/src/test/python/stacks/2.0.6/hooks/before-ANY/ 37a52df 



mvn clean test


Andrew Onischuk

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message