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/08/26 22:49:08 UTC

[jira] [Updated] (AMBARI-12588) Ambari Management Controller should log the creation of ExecutionCommand instances

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

Nate Cole updated AMBARI-12588:
-------------------------------
    Fix Version/s:     (was: 2.1.1)
                   2.1.2

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