kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Gustafson (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-7298) Concurrent DeleteRecords can lead to fatal OutOfSequence error in producer
Date Thu, 16 Aug 2018 00:13:00 GMT
Jason Gustafson created KAFKA-7298:
--------------------------------------

             Summary: 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


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)

Mime
View raw message