[
https://issues.apache.org/jira/browse/KAFKA-19690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated KAFKA-19690:
-----------------------------------
Fix Version/s: 4.1.1
> 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, 4.1.1
>
>
> 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)
