You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2015/03/13 20:31:39 UTC

[jira] [Updated] (AMBARI-10065) Performance: ActionScheduler loads too many objects per Stage iteration

     [ https://issues.apache.org/jira/browse/AMBARI-10065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nate Cole updated AMBARI-10065:
-------------------------------
    Summary: Performance: ActionScheduler loads too many objects per Stage iteration  (was: Performance: ActionSchedule loads too many objects per Stage iteration)

> Performance: ActionScheduler loads too many objects per Stage iteration
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-10065
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10065
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 2.0.0
>
>
> During analysis of a 400 node cluster, the ActionScheduler is loading too many stages, when it already has a handle to the correct stage.  The entire Request is not needed, when the code only checks the exclusive flag.



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