You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2017/05/30 18:53:04 UTC

[jira] [Created] (KAFKA-5347) OutOfSequence error should be fatal

Jason Gustafson created KAFKA-5347:
--------------------------------------

             Summary: OutOfSequence error should be fatal
                 Key: KAFKA-5347
                 URL: https://issues.apache.org/jira/browse/KAFKA-5347
             Project: Kafka
          Issue Type: Bug
            Reporter: Jason Gustafson
            Assignee: Apurva Mehta


If the producer sees an OutOfSequence error for a given partition, we currently treat it as an abortable error. This makes some sense because OutOfSequence won't prevent us from being able to send the EndTxn to abort the transaction. The problem is that the producer, even after aborting, still won't be able to send to the topic with an OutOfSequence. One way to deal with this is to ask the user to call {{initTransactions()}} again to bump the epoch, but this is a bit difficult to explain and could be dangerous since it renders zombie checking less effective. Probably we should just consider OutOfSequence fatal for the transactional producer.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)