[STORM-2426] First tuples fail after worker is respawn

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.2
• Fix Version/s: 2.0.0, 1.2.0, 1.1.2
• Component/s: storm-kafka-client
• Assignee: Stig Rohde Døssing
• Reporter: Antti Järvinen
• Created: 20/Mar/17 10:44
• Updated: 12/Oct/17 19:48
• Resolved: 12/Oct/17 19:48

Description

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.

Issue Links

• is related to: STORM-2541 Manual partition assignment doesn't work
• is related to: STORM-2542 Deprecate storm-kafka-client KafkaConsumer.subscribe API subscriptions on 1.x and remove them as options in 2.x