[
https://issues.apache.org/jira/browse/KAFKA-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713038#comment-15713038
]
Guozhang Wang commented on KAFKA-4473:
--------------------------------------
[~Thomas Schulz] Thanks for reporting this issue. I have a couple of questions
to follow up:
1. NotLeaderForPartitionException is a retriable error and hence it should be
keep retrying instead of throwing it out. If you turn on the debug level
logging do you see entries indicating it has been retrying?
2. Averagely how long it took in your testing environment to bounce a broker?
> 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)
