You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2016/11/15 03:47:58 UTC
[jira] [Resolved] (STORM-2006) Storm metrics feature improvement:
support per-worker level metrics aggregation
[ https://issues.apache.org/jira/browse/STORM-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim resolved STORM-2006.
---------------------------------
Resolution: Invalid
Closing in favor of STORM-2153.
> 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
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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)