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

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

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

    https://github.com/apache/storm/pull/1595#discussion_r72539748
  
    --- Diff: conf/defaults.yaml ---
    @@ -259,6 +259,10 @@ topology.disruptor.batch.size: 100
     topology.disruptor.batch.timeout.millis: 1
     topology.disable.loadaware: false
     topology.state.checkpoint.interval.ms: 1000
    +topology.metrics.aggregate.per.worker: false
    --- End diff --
    
    @HeartSaVioR Just to be clear, please don't take my comments to be a 
criticism of your work. You've done a fantastic job with metrics improvements.
    
    Through that work it's become apparent that the existing API for metrics 
consumers is lacking in a number of ways. I view this as an opportunity to 
correct that.
    
    We're incrementally moving toward semantic versioning. I'm not opposed to 
breaking backward compatibility with the existing metrics API and moving this 
branch to 2.x. The fact that master is "2.0" is just a technicality that can 
easily be changed.
    
    I'd like to fix the API to better reflect the work you've done, rather than 
to implement a one-off fix.


> Storm metrics feature improvement: support per-worker level metrics 
> aggregation
> -------------------------------------------------------------------------------
>
>                 Key: STORM-2006
>                 URL: https://issues.apache.org/jira/browse/STORM-2006
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>    Affects Versions: 1.1.0
>            Reporter: Jungtaek Lim
>            Assignee: Jungtaek Lim
>
> Storm provides per-task level metrics which could be huge when topology has a 
> number of tasks. 
> Task level metric is useful for determining load balance between tasks, but 
> it doesn't need to be time-series fashion.
> Before introducing topology level component like TopologyMaster for JStorm, 
> we can utilize SystemBolt to aggregate task level metrics to per-worker level 
> metrics.
> We should provide options and this feature should be turned off by default to 
> keep backward compatibility. 



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

Reply via email to