[
https://issues.apache.org/jira/browse/AMBARI-10065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361240#comment-14361240
]
Hudson commented on AMBARI-10065:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2030 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2030/])
AMBARI-10065. Performance: ActionScheduler loads too many objects per Stage
iteration (ncole) (ncole:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=88aed0b8e3f0db2e2726358a7622c4d5519ea709)
*
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatMonitor.java
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/KdcServerConnectionVerification.java
*
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessor.java
> 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
>
> Attachments: AMBARI-10065.patch
>
>
> 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)
