[STORM-2432] Storm-Kafka-Client Trident Spout Seeks Incorrect Offset With UNCOMMITTED_LATEST Strategy

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.x
• Fix Version/s: 2.0.0, 1.1.1, 1.2.0
• Component/s: storm-kafka-client
• Assignee: Hugo Da Cruz Louro
• Reporter: Raghav Kumar Gautam
• Created: 23/Mar/17 15:16
• Updated: 03/Jul/17 15:05
• Resolved: 26/Mar/17 17:16

Description

With UNCOMMITED_LATEST offset, Storm-Kafka-Client Trident Spout doesn't read all the data.
See worker logs for of the same topology with UNCOMMITED_EARLIEST as well as UNCOMITTED_LATEST.
The source topic has 3 partition and I publish data k000000-k000499(k000000, v000000 etc.)
In particular for k000000 value the data is not picked by spout at all.

Issue Links

• links to: GitHub Pull Request #2027