[
https://issues.apache.org/jira/browse/KAFKA-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716796#comment-15716796
]
Guozhang Wang commented on KAFKA-4473:
--------------------------------------
Thanks for the update [~Thomas Schulz]. I think what you observe still needs to
further fixing since naively for such retriable exceptions we should retry
infinitely since otherwise there is still a risk of dropping a message on the
floor and proceed.
I will try to propose a ultimate solution for this while working on
exactly-once semantics and hence to keep this JIRA open for now.
> KafkaStreams does *not* guarantee at-least-once delivery
> --------------------------------------------------------
>
> 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
> Priority: Critical
>
> 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)
