You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Nahappan Somasundaram (JIRA)" <ji...@apache.org> on 2016/05/21 02:42:12 UTC

[jira] [Created] (AMBARI-16806) AMS Collector is not automatically being configured for auto-start during blueprint deployment

Nahappan Somasundaram created AMBARI-16806:
----------------------------------------------

             Summary: AMS Collector is not automatically being configured for auto-start during blueprint deployment
                 Key: AMBARI-16806
                 URL: https://issues.apache.org/jira/browse/AMBARI-16806
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.4.0
            Reporter: Nahappan Somasundaram
            Assignee: Nahappan Somasundaram
             Fix For: 2.4.0


When using blueprint to deploy a cluster, if settings section is not specified, AMBARI_METRICS::METRICS_COLLECTOR is not flagged for auto start, even though it's stack definition /var/lib/ambari-server/resources/common-services/AMBARI_METRICS/0.1.0/metainfo.xml has the <recovery_enabled>true</recovery_enabled> entry.



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