[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044861#comment-16044861 ]
Apurva Mehta commented on KAFKA-5415: ------------------------------------- [~guozhang] has found the bug and will file the PR. Assigning to him. > TransactionCoordinator gets stuck in PrepareCommit state > -------------------------------------------------------- > > Key: KAFKA-5415 > URL: https://issues.apache.org/jira/browse/KAFKA-5415 > Project: Kafka > Issue Type: Bug > Reporter: Apurva Mehta > Assignee: Guozhang Wang > Priority: Blocker > Labels: exactly-once > Fix For: 0.11.0.0 > > Attachments: 6.tgz > > > This has been revealed by the system test failures on jenkins. > The transaction coordinator seems to get into a path during the handling of > the EndTxnRequest where it returns an error (possibly a NOT_COORDINATOR or > COORDINATOR_NOT_AVAILABLE error, to be revealed by > https://github.com/apache/kafka/pull/3278) to the client. However, due to > network instability, the producer is disconnected before it receives this > error. > As a result, the transaction remains in a `PrepareXX` state, and future > `EndTxn` requests sent by the client after reconnecting result in a > `CONCURRENT_TRANSACTION` error code. Hence the client gets stuck and the > transaction never finishes, as expiration isn't done from a PrepareXX state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)