[
https://issues.apache.org/jira/browse/STORM-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945190#comment-13945190
]
Jon logan commented on STORM-261:
---------------------------------
I haven't actually verified this, but when it's scheduled out of the topology,
shouldn't it stop receiving new data? In that case, the only data it outputs
would be older buffered data, or if there was a thread (or similar)-type tick
outputting tuples. Otherwise, it should just be sitting there, wasting
resources, but not outputting data...I think?
> Workers should commit suicide if not scheduled any more.
> --------------------------------------------------------
>
> Key: STORM-261
> URL: https://issues.apache.org/jira/browse/STORM-261
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Affects Versions: 0.9.2-incubating
> Reporter: Robert Joseph Evans
> Priority: Minor
>
> I know this is a bit far fetched.
> If for some reason a supervisor dies and does not come back up again, dead
> HDD for example, but the workers remain up, and the scheduler decides to move
> the worker to a new host, a rebalance for instance, the old workers will
> never go away. Ideally the worker should know that it is not running in the
> correct place any more and die instead of waiting for the supervisor to kill
> it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
