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

Hadoop QA commented on AMBARI-12588:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12748023/AMBARI-12588.patch.2
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {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:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3502//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3502//console

This message is automatically generated.

> Ambari Management Controller should log the creation of ExecutionCommand 
> instances
> ----------------------------------------------------------------------------------
>
>                 Key: AMBARI-12588
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12588
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>             Fix For: 2.1.1
>
>         Attachments: AMBARI-12588.patch.2
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> The AmbariManagementControllerImpl class does not currently log the creation 
> of ExecutionCommand instances used for installing and starting the services 
> in a cluster. 
> This is problematic, particularly for Blueprint installs of larger clusters.  
> The controller class should log the basic information regarding the 
> ExecutionCommand, since it would be very useful in debugging large clusters 
> involving lots of concurrency.  
> I'm working on a fix for this, and will be submitting a patch shortly.  



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

Reply via email to