You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Aleksandr Savonin (Jira)" <ji...@apache.org> on 2026/05/21 13:57:00 UTC

[jira] [Commented] (FLINK-39723) KafkaTableITCase.testExactlyOnceSink fails due to transactional ID reuse across test runs

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

Aleksandr Savonin commented on FLINK-39723:
-------------------------------------------

Could someone please assign to me?

> KafkaTableITCase.testExactlyOnceSink fails due to transactional ID reuse across test runs
> -----------------------------------------------------------------------------------------
>
>                 Key: FLINK-39723
>                 URL: https://issues.apache.org/jira/browse/FLINK-39723
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka
>            Reporter: Aleksandr Savonin
>            Priority: Major
>
> KafkaTableITCase.testExactlyOnceSink intermittently fails in CI with ProducerFencedException caused by transactional producer state leaking between test runs on the same Kafka broker instance.
> Observed in: CI run https://github.com/apache/flink-connector-kafka/actions/runs/26227821749
>  
> Ideas/potential fixes to think about:
>  - Use randomized/unique transactional ID prefixes per test run (similar to how topic names already use random UUIDs)
>   - Or explicitly abort any open transactions with the same ID before the test starts
>   - Or ensure the Kafka container is fully restarted between parameterized variants that share transactional ID space



--
This message was sent by Atlassian Jira
(v8.20.10#820010)