[jira] [Commented] (STORM-1593) Nimbus indicator for when a Topology finished processing all tuples

["Abhishek Agarwal (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STORM-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175203#comment-15175203 ] 

Abhishek Agarwal commented on STORM-1593:
-----------------------------------------

It sounds useful. Just to confirm the exact use case, you want to kill the topology only after all un-acked messages have been acked. 

> 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)