[ 
https://issues.apache.org/jira/browse/KAFKA-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045857#comment-16045857
 ] 

ASF GitHub Bot commented on KAFKA-5428:
---------------------------------------

GitHub user hachikuji opened a pull request:

    https://github.com/apache/kafka/pull/3298

    KAFKA-5428: Transactional producer should only abort batches in fatal error 
state

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/hachikuji/kafka KAFKA-5428

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/3298.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3298
    
----
commit 5bd97c0e10ba73a79299d40d3223718acfe7e97d
Author: Jason Gustafson <ja...@confluent.io>
Date:   2017-06-11T07:18:05Z

    KAFKA-5428: Transactional producer should only abort batches in 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)

Reply via email to