ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nahappan Somasundaram (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-16806) AMS Collector is not automatically being configured for auto-start during blueprint deployment
Date Mon, 23 May 2016 01:47:12 GMT

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

Nahappan Somasundaram updated AMBARI-16806:
-------------------------------------------
    Status: Patch Available  (was: In Progress)

> 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
>            Priority: Blocker
>             Fix For: 2.4.0
>
>         Attachments: blueprints2.json, hg2.json, rb47688.patch
>
>
> 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.
> Create the blueprint: 
> curl -u admin:admin -H "X-Requested-By: ambari" -X POST -d @/tmp/blueprints2.json http://localhost:8080/api/v1/blueprints/bp2
> Deploy the cluster: 
> curl -u admin:admin -H "X-Requested-By: ambari" -X POST -d @/tmp/hg2.json http://localhost:8080/api/v1/clusters/c1



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

Mime
View raw message