You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Devang (JIRA)" <ji...@apache.org> on 2014/10/30 15:20:34 UTC
[jira] [Created] (STORM-543) Storm failing all input messages
(although successfully processed) post restarting on the same supervisor
slot
Devang created STORM-543:
----------------------------
Summary: Storm failing all input messages (although successfully processed) post restarting on the same supervisor slot
Key: STORM-543
URL: https://issues.apache.org/jira/browse/STORM-543
Project: Apache Storm
Issue Type: Bug
Affects Versions: 0.9.2-incubating
Reporter: Devang
Steps to simulate the behaviour,
1. Run topology(spout as single instance and multiple instances of bolts)
on multiple workers.
2. Identify the slot on which the single spout instance is running (from STORM UI) and kill it (using kill -9)
3. See if the supervisor started the worker on the same supervisor port. If not then repeat step 2 untill you get supervisor on the same slot as previous one.
4. Pump in a message into the topology.
5. You will see message being processed successfully but acker failing the tuple after the message times out (defaults to 30 secs).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)