You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/07/30 05:32:04 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14647124#comment-14647124 ]
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/12747877/AMBARI-12588.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3496//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
>
> 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)