ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (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.
Date Wed, 26 Aug 2015 11:20:45 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-12871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712955#comment-14712955
] 

Hudson commented on AMBARI-12871:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3324 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3324/])
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. (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6ccabc61e451347d1b3168d8fe1eb7a98d6bd6b6)
* ambari-server/src/test/python/stacks/2.0.6/hooks/before-ANY/test_before_any.py
* ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py


> 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)

Mime
View raw message