[
https://issues.apache.org/jira/browse/AMBARI-10065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361046#comment-14361046
]
Hadoop QA commented on AMBARI-10065:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704493/AMBARI-10065.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2024//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2024//console
This message is automatically generated.
> 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)
