[jira] [Resolved] (STORM-2426) First tuples fail after worker is respawn

["Stig Rohde Døssing (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STORM-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stig Rohde Døssing resolved STORM-2426.
---------------------------------------
       Resolution: Fixed
         Assignee: Stig Rohde Døssing
    Fix Version/s: 1.1.2
                   1.2.0
                   2.0.0

This should no longer be an issue once we move away from the Named/PatternSubscription Subscription implementations. Those implementations are no longer an option in 2.0.0, and are deprecated from 1.2.0. Please switch to using the ManualPartitionSubscription class when configuring KafkaSpoutConfig. ManualPartitionSubscription should work from 1.1.2 on.

> 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
>            Assignee: Stig Rohde Døssing
>             Fix For: 2.0.0, 1.2.0, 1.1.2
>
>         Attachments: 2017-03-20-Kafka-spout-issue.txt, 2017-03-21-Timeout-ticks.txt
>
>
> Topology with two Kafka spouts (org.apache.storm.kafka.spout.KafkaSpout) reading from two different topics with same consumer group ID. 
> 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.4.14#64029)