[
https://issues.apache.org/jira/browse/KAFKA-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941193#comment-15941193
]
Apurva Mehta commented on KAFKA-4817:
-------------------------------------
There is some subtlety in the idempotent producer semantics. This patch only
guarantees idempotent production upto the point where an error has to be
returned to the user. Once we hit a such a non-recoverable error, we can no
longer guarantee message ordering nor idempotence without additional logic at
the application level.
In particular, if an application wants guaranteed message order without
duplicates, then it needs to do the following in the error callback:
Close the producer so that no queued batches are sent. This is important for
guaranteeing ordering.
Read the tail of the log to inspect the last message committed. This is
important for avoiding duplicates.
> Implement idempotent producer
> -----------------------------
>
> Key: KAFKA-4817
> URL: https://issues.apache.org/jira/browse/KAFKA-4817
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, core, producer
> Reporter: Jason Gustafson
> Assignee: Apurva Mehta
> Fix For: 0.11.0.0
>
>
> This task covers the implementation of the idempotent producer for KIP-98.
> This covers both the necessary changes on the server-side and client-side
> changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
