You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/03/24 21:57:00 UTC

[jira] [Resolved] (KAFKA-9749) TransactionMarkerRequestCompletionHandler should treat storage exceptions as retriable

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

Jason Gustafson resolved KAFKA-9749.
------------------------------------
    Fix Version/s: 2.4.2
                   2.3.2
                   2.5.0
       Resolution: Fixed

> TransactionMarkerRequestCompletionHandler should treat storage exceptions as retriable
> --------------------------------------------------------------------------------------
>
>                 Key: KAFKA-9749
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9749
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.5.0
>            Reporter: Bob Barrett
>            Assignee: Bob Barrett
>            Priority: Major
>             Fix For: 2.5.0, 2.3.2, 2.4.2
>
>
> If `TransactionMarkerRequestCompletionHandler` handles a `KafkaStorageException`, it throws an IllegalStateException rather than retrying. This leaves the corresponding transactional ID in state PendingAbort, where it gets stuck, because any further EndTxn or InitProducerId call will fail with a CONCURRENT_TRANSACTIONS error. We should retry these errors when writing transaction markers.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)