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

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_r72479602
  
    --- 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 
    If I'm following the code/conversation correctly, this flag essentially 
changes the IMetricConsumer interface (specifically the value set in the 
DataPoint class - which is of type Object).  That makes me very uneasy.
    
    Is there a way to make the interface more strongly typed?
    
    Thinking out loud: What about splitting the interface in two: One that does 
aggregation and one that doesn't, then switching calls based on which interface 
is implemented?
    
    I'm not opposed to breaking backwards compatibility and bumping up the 
major version if necessary. In other words I'd rather see a clean design than 
preserve backwards compatibility with respect to the metrics features.


> 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