Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 28 Jul 2015 15:36:04 +0000 (UTC)
From: "Robert Nettleton (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12849652.1438097753000.308283.1438097764519@Atlassian.JIRA>
In-Reply-To: <JIRA.12849652.1438097753000@Atlassian.JIRA>
References: <JIRA.12849652.1438097753000@Atlassian.JIRA>
 <JIRA.12849652.1438097753227@arcas>
Subject: [jira] [Created] (AMBARI-12567) Blueprint provisioning code needs
 more debug logging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Robert Nettleton created AMBARI-12567:
-----------------------------------------

             Summary: Blueprint provisioning code needs more debug logging
                 Key: AMBARI-12567
                 URL: https://issues.apache.org/jira/browse/AMBARI-12567
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.1.0
            Reporter: Robert Nettleton
            Assignee: Robert Nettleton
             Fix For: 2.1.1


The new Blueprint dynamic provisioning mechanism, added in Ambari 2.1.0, does not log much useful information when handling the setup of a cluster.  

This is particularly problematic in large cluster deployments that use the predicate syntax in the cluster creation template.  

Logging should be added to the TopologyManager and other classes in this area of Blueprints in order to facilitate simpler debugging of problems, particularly problems that occur in large-scale, high-concurrency environments.  

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)