[
https://issues.apache.org/jira/browse/STORM-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14578101#comment-14578101
]
Derek Dagit commented on STORM-856:
-----------------------------------
Actually, I think it is serialized, but it is nested down one more level than
before the thrift serialization change.
[~kabhwan], I think it is a [simple
fix|https://github.com/apache/storm/compare/master...d2r:storm-856-use-ser-delay-secs];
if you (or the cat) want to make a pull request, it would be OK :) Otherwise
I will put up a pull request shortly when I can confirm it works.
I agree, if this condition happens in the cluster, then it takes some effort to
restore nimbus to a working state while keeping running topologies.
Unfortunately, I will mark it as a blocker.
> 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
> Assignee: Derek Dagit
> Priority: Blocker
>
> 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)
