[
https://issues.apache.org/jira/browse/KAFKA-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-4473:
---------------------------------
Resolution: Fixed
Fix Version/s: 0.10.2.0
Status: Resolved (was: Patch Available)
Issue resolved by pull request 2249
[https://github.com/apache/kafka/pull/2249]
> RecordCollector should handle retriable exceptions more strictly
> ----------------------------------------------------------------
>
> Key: KAFKA-4473
> URL: https://issues.apache.org/jira/browse/KAFKA-4473
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.10.1.0
> Reporter: Thomas Schulz
> Assignee: Damian Guy
> Priority: Critical
> Labels: architecture
> Fix For: 0.10.2.0
>
>
> 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?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
