[ 
https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335356#comment-15335356
 ] 

Jungtaek Lim commented on AMBARI-17080:
---------------------------------------

Additionally, we need to modify some parameters for Storm:

- metrics.reporter.register : should be removed
- storm.cluster.metrics.consumer.register : should be added with default value 
here
  - {code}[{"class": 
"org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter"}]{code}
- topology.metrics.consumer.register : can be added again, with or without 
default value
  - {code}[{'class': 
'org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink', 
'parallelism.hint': 1}]{code}

Regarding topology.metrics.consumer.register, I addressed several patches for 
performance on storm side, but if we're still in doubt about performance drop, 
it would be possible to leave it to empty array, and document how to set up 
topology metrics consumer.

I don't have an experience about changing parameter, so I'd be happy if someone 
guides me how to do it. If someone could resolve this for me I'd be happy, too.

> Support Storm 1.0 in Ambari Metrics for Storm
> ---------------------------------------------
>
>                 Key: AMBARI-17080
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17080
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.4.0
>            Reporter: Jungtaek Lim
>         Attachments: AMBARI-17080-v1.patch, AMBARI-17080-v2.patch
>
>
> Since there was package name change on Apache Storm 1.0.0, Ambari Metrics 
> Reporter / Sink for Storm will not work when Ambari supports Apache Storm 
> 1.0.0 or upper.
> This issue is for addressing this. 
> Please note that it will incur compile failure unless Ambari Metrics pom file 
> depends on Storm 1.x version, so decision for version of Storm should be made 
> first.



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

Reply via email to