You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2015/09/18 00:39:04 UTC

[jira] [Resolved] (STORM-1007) Add more metrics to DisruptorQueue

     [ https://issues.apache.org/jira/browse/STORM-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jungtaek Lim resolved STORM-1007.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11.0

Thanks [~wangli1426],
I merged into master. Keep up the good work.

> Add more metrics to DisruptorQueue
> ----------------------------------
>
>                 Key: STORM-1007
>                 URL: https://issues.apache.org/jira/browse/STORM-1007
>             Project: Apache Storm
>          Issue Type: New Feature
>            Reporter: Li Wang
>            Assignee: Li Wang
>             Fix For: 0.11.0
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> The metrics of the queues for each component are very helpful to reason about the performance issues of a topology.
> For instance, for the applications with strong time constraint (e.g., threat detection), if the elements in the input queue of a bolt have a long sojourn time, it indicates that the user should increase the parallelism of that bolt to reduce the processing delay.
> However, the metrics on the DisruptorQueue currently available are limited. More useful metrics, such as average sojourn time and average throughput are expected.



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