[
https://issues.apache.org/jira/browse/AMBARI-12588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981399#comment-14981399
]
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:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4098//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.3
>
> 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)
