You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Antti Järvinen (JIRA)" <ji...@apache.org> on 2017/03/20 10:45:41 UTC
[jira] [Updated] (STORM-2426) First tuples fail after worker is
respawn
[ https://issues.apache.org/jira/browse/STORM-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antti Järvinen updated STORM-2426:
----------------------------------
Description:
Topology with two Kafka spouts (org.apache.storm.kafka.spout.KafkaSpout) reading from two different topics.
1. Kill the only worker process for topology
2. Storm creates new worker
3. Kafka starts rebalancing (log line 15-16)
4. Kafka rebalancing done (log line 18-19)
5. Kafka topics read and tuples emitted (log line 28-29)
6. Tuples immediately fail (log line 30-33)
The delay between tuples emitted and tuples failing is just some 10 ms. No bolts in topology received the tuples.
What could cause this? The assumption is that there are uncommitted messages in Spout when it is killed and those are retried.
was:
Topology with two Kafka spouts (org.apache.storm.kafka.spout.KafkaSpout) reading from two different topics.
1. Kill the only worker process for topology
2. Storm creates new worker
3. Kafka starts rebalancing (log line 15-16)
4. Kafka rebalancing done (log line 18-19)
5. Kafka topics read and tuples emitted (log line 28-29)
6. Tuples immediately fail (log line 30-33)
The delay between tuples emitted and tuples failing is just some 10 ms. No bolts in topology received the tuples.
What could cause this?
> First tuples fail after worker is respawn
> -----------------------------------------
>
> Key: STORM-2426
> URL: https://issues.apache.org/jira/browse/STORM-2426
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka-client
> Affects Versions: 1.0.2
> Reporter: Antti Järvinen
> Attachments: 2017-03-20-Kafka-spout-issue.txt
>
>
> Topology with two Kafka spouts (org.apache.storm.kafka.spout.KafkaSpout) reading from two different topics.
> 1. Kill the only worker process for topology
> 2. Storm creates new worker
> 3. Kafka starts rebalancing (log line 15-16)
> 4. Kafka rebalancing done (log line 18-19)
> 5. Kafka topics read and tuples emitted (log line 28-29)
> 6. Tuples immediately fail (log line 30-33)
> The delay between tuples emitted and tuples failing is just some 10 ms. No bolts in topology received the tuples.
> What could cause this? The assumption is that there are uncommitted messages in Spout when it is killed and those are retried.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)