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

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

GitHub user hachikuji opened a pull request:

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

    KAFKA-5342: Clarify fatal/abortable exceptions used in producer

    

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

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

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

    https://github.com/apache/kafka/pull/3716.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 #3716
    
----
commit cdbe4fcfb5ae86a3a93f0954b0889f1d84e2ae93
Author: Jason Gustafson <[email protected]>
Date:   2017-08-22T21:55:57Z

    KAFKA-5342: Clarify fatal/abortable exceptions used in producer

----


> Distinguish abortable failures in transactional producer
> --------------------------------------------------------
>
>                 Key: KAFKA-5342
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5342
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, core, producer 
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>             Fix For: 0.11.0.1
>
>
> The transactional producer distinguishes two classes of user-visible errors:
> 1. Abortable errors: these are errors which are fatal to the ongoing 
> transaction, but which can be successfully aborted. Essentially any error in 
> which the producer can still expect to successfully send EndTxn to the 
> transaction coordinator is abortable.
> 2. Fatal errors: any error which is not abortable is fatal. For example, a 
> transactionalId authorization error is fatal because it would also prevent 
> the TC from receiving the EndTxn request.
> At the moment, it's not clear how the user would know how they should handle 
> a given failure. One option is to add an exception type to indicate which 
> errors are abortable (e.g. AbortableKafkaException). Then any other exception 
> could be considered fatal.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to