[KAFKA-4473] RecordCollector should handle retriable exceptions more strictly

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.10.1.0
• Fix Version/s: 0.10.2.0
• Component/s: streams
• Labels: architecture
• Assignee: Damian Guy
• Reporter: Thomas Schulz
• Created: 01/Dec/16 11:56
• Updated: 20/Dec/16 18:00
• Resolved: 20/Dec/16 17:59

Description

see: https://groups.google.com/forum/#!topic/confluent-platform/DT5bk1oCVk8

There is probably a bug in the RecordCollector as described in my detailed Cluster test published in the aforementioned post.

The class RecordCollector has the following behavior:

• if there is no exception, add the message offset to a map
• otherwise, do not add the message offset and instead log the above statement

Is it possible that this offset map contains the latest offset to commit? If so, a message that fails might be overriden be a successful (later) message and the consumer commits every message up to the latest offset?

Issue Links

• links to: GitHub Pull Request #2249