[AMBARI-12412] Storm service won't work with metrics after Blueprint deployment

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 2.1.0
• Fix Version/s: 2.3.0
• Component/s: ambari-server
• Assignee: Bob Nettleton
• Reporter: Bob Nettleton
• Created: 14/Jul/15 19:20
• Updated: 25/Sep/15 22:59

Description

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:

<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>

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.