You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2015/06/08 23:44:00 UTC
[jira] [Commented] (STORM-856) If nimbus goes down with a delayed
kill topo cmd, it never comes up
[ https://issues.apache.org/jira/browse/STORM-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577895#comment-14577895 ]
Jungtaek Lim commented on STORM-856:
------------------------------------
We would be better to have more informations to address this.
- Is it always reproducible? Or occasionally?
- What messages are printed out when nimbus is crashed? Are stack traces made on each crash pointing to same code line?
> 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)