You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/01/09 19:12:00 UTC

[jira] [Commented] (KAFKA-9287) Transaction completion may block unnecessarily after abortable error

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

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

hachikuji commented on pull request #7799: KAFKA-9287; Fix unneeded delay before failing pending transaction commit
URL: https://github.com/apache/kafka/pull/7799
 
 
   
 
----------------------------------------------------------------
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


> Transaction completion may block unnecessarily after abortable error
> --------------------------------------------------------------------
>
>                 Key: KAFKA-9287
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9287
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>
> This was discovered while investigating the delay in `AuthorizerIntegrationTest.testTransactionalProducerTopicAuthorizationExceptionInCommit` which typically takes 35 seconds rather than 5 seconds like most of these other tests in this class. There is an edge case on transaction completion if an AddPartitionsToTxn request fails with an abortable error in which the producer may be left blocking in `NetworkClient.poll` without failing the pending commit and without any pending requests. Ultimately the test case was blocking the full 30s request timeout before failing the transaction.



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