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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

hachikuji commented on pull request #8336: KAFKA-9749: TransactionMarkerRequestCompletionHandler should treat KAFKA_STORAGE_…
URL: https://github.com/apache/kafka/pull/8336
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>
> 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)