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/06/11 07:15:18 UTC

[jira] [Updated] (KAFKA-5428) Transactional producer aborts batches incorrectly in abortable error state

     [ https://issues.apache.org/jira/browse/KAFKA-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson updated KAFKA-5428:
-----------------------------------
    Description: We currently abort batches blindly if we are in any error state. We should only do this if we are in a fatal error state. Otherwise, we risk OutOfOrderSequence errors if a failed produce request had actually been written successfully to the topic.  (was: We currently abort batches blindly if we are in any error state. We should only do this if we are in a fatal error state.)

> Transactional producer aborts batches incorrectly in abortable error state
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-5428
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5428
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, core, producer 
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Blocker
>             Fix For: 0.11.0.0
>
>
> We currently abort batches blindly if we are in any error state. We should only do this if we are in a fatal error state. Otherwise, we risk OutOfOrderSequence errors if a failed produce request had actually been written successfully to the topic.



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