You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2025/10/02 13:20:00 UTC
[jira] [Commented] (KAFKA-19690) Unexpected Fatal error InvalidTxnStateException on Kafka Streams (KIP-890)
[ https://issues.apache.org/jira/browse/KAFKA-19690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024273#comment-18024273 ]
Chia-Ping Tsai commented on KAFKA-19690:
----------------------------------------
4.1: https://github.com/apache/kafka/commit/a10c1f3ea1454dbd644ea65a885c965529e1d37d
> Unexpected Fatal error InvalidTxnStateException on Kafka Streams (KIP-890)
> --------------------------------------------------------------------------
>
> Key: KAFKA-19690
> URL: https://issues.apache.org/jira/browse/KAFKA-19690
> Project: Kafka
> Issue Type: Bug
> Components: core, streams
> Affects Versions: 4.1.0
> Reporter: Ritika Reddy
> Assignee: Ritika Reddy
> Priority: Major
> Fix For: 3.9.2, 4.2.0
>
>
> We are seeing cases where a Kafka Streams (KS) thread stalls for ~20 seconds, resulting in a visible gap in the logs. During this stall, the broker correctly aborts the open transaction (triggered by the 10-second transaction timeout). So far, this is expected behavior. However, when the KS thread resumes, instead of receiving the expected InvalidProducerEpochException (which we already handle gracefully as part of transaction abort), the client is instead hit with an InvalidTxnStateException. KS currently treats this as a fatal error, causing the application to fail.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)