[
https://issues.apache.org/jira/browse/STORM-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401048#comment-15401048
]
ASF GitHub Bot commented on STORM-2006:
---------------------------------------
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1595
@ptgoetz @harshach @abhishekagarwal87
I just had the limitations of current metrics feature only in my mind, but
it would be better to write it down and share to persuade the need for new
metrics feature.
I didn't grant the wiki access so I just use google doc. Please let me know
if we want to have this in Apache infra. I can move this out to wiki, or just
post to dev@ mailing list.
https://docs.google.com/document/d/11H3STXr2QTnfOqisgOnvNt8TjXS_cSqb86VM6vdAo8s/edit?usp=sharing
@unsleepy22 AFAIK you worked on the change of JStorm metrics. Could you
check the doc and confirm that JStorm metrics feature addressed the limitations
of Storm metrics feature?
> 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)
