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

ASF GitHub Bot commented on STORM-1723:
---------------------------------------

Github user abhishekagarwal87 commented on a diff in the pull request:

    https://github.com/apache/storm/pull/1352#discussion_r61555323
  
    --- Diff: conf/defaults.yaml ---
    @@ -285,3 +285,6 @@ pacemaker.kerberos.users: []
     #default storm daemon metrics reporter plugins
     storm.daemon.metrics.reporter.plugins:
          - "org.apache.storm.daemon.metrics.reporters.JmxPreparableReporter"
    --- End diff --
    
    can't we piggyback on codahale to report these metrics? We can have one 
more config
    ```storm.cluster.metrics.reporter.plugins:
       - "org.apache.storm.daemon.metrics.reporters.JmxPreparableReporter"
    ```
    I haven't gone through diff in nimbus completely but I suppose they can be 
modeled as gauages. It would be lot more simplified in my opinion.


> Introduce ClusterMetricsConsumer
> --------------------------------
>
>                 Key: STORM-1723
>                 URL: https://issues.apache.org/jira/browse/STORM-1723
>             Project: Apache Storm
>          Issue Type: New Feature
>          Components: storm-core
>    Affects Versions: 2.0.0, 1.0.1
>            Reporter: Jungtaek Lim
>            Assignee: Jungtaek Lim
>
> NOTE: This issue is already discussed shortly. Please refer 
> [here|http://mail-archives.apache.org/mod_mbox/storm-dev/201604.mbox/%3CCAF5108hDCcMKxLXKUYLReOoKkNNdgW2YudweR+mKr=1hlsl...@mail.gmail.com%3E]
>  for details.
> This issue focuses to introduce ClusterMetricsConsumer and provide interface 
> to let users plugin their consumers.
> ClusterMetricsConsumers will be attached to Nimbus, and leader of Nimbus will 
> push cluster related metrics to ClusterMetricsConsumer.
> Requirements of ClusterMetricsConsumer are here:
> - Only leader of Nimbus should publish cluster metrics to consumer.
> - Nimbus shouldn't be affected by crashing or heavy latency on consumer.
> - Consumer should have resilient when crashing or Nimbus should take care of.



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

Reply via email to