[
https://issues.apache.org/jira/browse/KAFKA-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586339#comment-16586339
]
Matthias J. Sax commented on KAFKA-7298:
----------------------------------------
[~hachikuji] Should this be back ported to older branches, too?
> Concurrent DeleteRecords can lead to fatal OutOfSequence error in producer
> --------------------------------------------------------------------------
>
> Key: KAFKA-7298
> URL: https://issues.apache.org/jira/browse/KAFKA-7298
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
> Fix For: 2.0.1
>
>
> We have logic in the producer to handle unknown producer errors. Basically
> when the producer gets an unknown producer error, it checks whether the log
> start offset is larger than the last acknowledged offset. If it is, then we
> know the error is spurious and we reset the sequence number to 0, which the
> broker will then accept.
> It can happen after a DeleteRecords call, however, that the only record
> remaining in the log is a transaction marker, which does not have a sequence
> number. The error we get in this case is OUT_OF_SEQUENCE rather than
> UNKNOWN_PRODUCER, which is fatal.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
