[STORM-2719] Trident Kafka Spout Emitters do not get full partition information in getOrderedPartitions()

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.1.1
• Component/s: storm-kafka-client, trident
• Assignee: Unassigned
• Reporter: Janith Kaiprath Valiyalappil
• Created: 03/Sep/17 17:28
• Updated: 05/Sep/17 04:57
• Resolved: 03/Sep/17 18:08

Description

The storm kakfa trident spout uses the KafkaTridentSpoutTopicPartitionRegistry, to get partition information. The coordinator calls the getTopicPartitions() method to get partition information and passes it to the emitters. But this partition information will not be accurate as all instances of KafkaTridentSpoutTopicPartitionRegistry will not be updated with full partition information.

The update to the registry is done when the consumer subscribes using KafkaSpoutConsumerRebalanceListener. This calls the KafkaTridentSpoutTopicPartitionRegistry.INSTANCE.addAll(partitions); These calls would only update the registry in that particular worker with partition information for consumers in that worker.

So when the coordinator calls the getOrderedPartitions() and passes it to each emitter by calling getOrderedPartitions(), the full partition information will not be present. The only probable case this would work is if the emitters and coordinators were on the same worker.

Issue Links

• duplicates: STORM-2691 storm-kafka-client Trident spout implements the Trident interface incorrectly
• duplicates: STORM-2473 KafkaTridentSpoutOpaque's implementation is incorrect.