[
https://issues.apache.org/jira/browse/AMBARI-12412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-12412:
-----------------------------------
Fix Version/s: (was: 2.1.2)
2.2.0
> Storm service won't work with metrics after Blueprint deployment
> ----------------------------------------------------------------
>
> Key: AMBARI-12412
> URL: https://issues.apache.org/jira/browse/AMBARI-12412
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.2.0
>
>
> After deploying a Storm cluster using a Blueprint, the Storm services are no
> properly integrated with Ambari Metrics, and so no Metrics-related data is
> available for Storm after this deployment.
> The following properties:
> {code}
> <property>
> <name>topology.metrics.consumer.register</name>
> <value>[{'class':
> 'org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink',
> 'parallelism.hint': 1}]</value>
> <description>Topology metrics consumer register parameters.</description>
> </property>
> <property>
> <name>metrics.reporter.register</name>
>
> <value>org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter</value>
> <description>Topology metrics reporter.</description>
> </property>
> {code}
> currently need to be added manually to the Blueprint in order to property
> integrate the Storm services and Ambari Metrics.
> Some investigation is required in order to determine the source of the
> problem. This is likely an issue in either the Blueprints processor or the
> stack defintions for Ambari. This properties are currently defined in the
> AMS service in the stacks, but are not defined in the Storm service
> definitions.
> This type of deployment works properly in the UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
