[jira] [Commented] (STORM-2006) Storm metrics feature improvement: support per-worker level metrics aggregation

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

Github user harshach commented on the issue:

    https://github.com/apache/storm/pull/1595
  
    @HeartSaVioR It will be good to have confluent wiki setup like other projects in apache do. We can have proposal setup there and go through the process of discussion in mailing list. I would start on user list so that we can hear from any existing or future user opinions as well.


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