[
https://issues.apache.org/jira/browse/STORM-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175667#comment-15175667
]
Robert Joseph Evans commented on STORM-1593:
--------------------------------------------
That sounds not too difficult to do. We would need to add some state to the
heartbeat to include the number of outstanding tuples for each spout, which
would be a useful metric to have anyways. I am not sure that I would just make
it a green indicator though. That seems very single use. I would rather have
the number of outstanding tuples currently available both through zookeeper and
through a Metric.
> Nimbus indicator for when a Topology finished processing all tuples
> -------------------------------------------------------------------
>
> Key: STORM-1593
> URL: https://issues.apache.org/jira/browse/STORM-1593
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-core
> Reporter: Michael Schonfeld
> Priority: Minor
>
> Every time we want to update topologies, we routinely find ourselves waiting
> aimlessly for topologies to "fully finish" processing. We never truly know
> when a topology is actually still processing tuples, and when it's really
> done... Unless of course we wait for a full 10m window showing zeros in
> Nimbus's topology stats table.
> I think it'd be beneficial to add some sort of a "Green" indicator in Nimbus,
> showing when a deactivated topology has ~0 tuples ringing through it. Would
> using the queue send/rcv population metric be correct for this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
