[
https://issues.apache.org/jira/browse/STORM-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577984#comment-14577984
]
Jungtaek Lim commented on STORM-856:
------------------------------------
Sorry, assigning is by accident, my cat just walks on Macbook.
Btw, once it is triggered users cannot restore from this situation unless they
remove state from zk by hand.
(But I don't expect users to remove it manually.)
I think it should be marked as critical or even higher.
> If nimbus goes down with a delayed kill topo cmd, it never comes up
> -------------------------------------------------------------------
>
> Key: STORM-856
> URL: https://issues.apache.org/jira/browse/STORM-856
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Derek Dagit
>
> 1. Describe observed behavior.
> nimbus is in a crash loop
> 2. What is the expected behavior?
> nimbus stays up
> 3. Outline the steps to reproduce the problem.
> launch a topo
> kill topo with `storm kill $topo` (no wait argument, so it defaults to 30s)
> Immediately restart nimbus
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
