[
https://issues.apache.org/jira/browse/STORM-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111225#comment-14111225
]
ASF GitHub Bot commented on STORM-433:
--------------------------------------
Github user nathanmarz commented on a diff in the pull request:
https://github.com/apache/incubator-storm/pull/236#discussion_r16738230
--- Diff: storm-core/src/clj/backtype/storm/daemon/worker.clj ---
@@ -40,8 +40,13 @@
))
assignment)))))
+(defn update-queue-stats [executors]
+ (doseq [executor executors]
+ (.update-queue-stats executor)))
--- End diff --
You need a type hint here to avoid reflection
> Give users visibility to the depth of queues at each bolt
> ---------------------------------------------------------
>
> Key: STORM-433
> URL: https://issues.apache.org/jira/browse/STORM-433
> Project: Apache Storm (Incubating)
> Issue Type: Wish
> Reporter: Dane Hammer
> Priority: Minor
>
> I envision being able to browse the Storm UI and see where queues of tuples
> are backing up.
> Today if I see latencies increasing at a bolt, it may not be due to anything
> specific to that bolt, but that it is backed up behind an overwhelmed bolt
> (which has too low of parallelism or too high of latency).
> I would expect this could use sampling like the metrics reported to the UI
> today, and just retrieve data from netty about the state of the queues. I
> wouldn't imagine supporting zeromq on the first pass.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
