[
https://issues.apache.org/jira/browse/FLINK-39218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18112123#comment-18112123
]
Yuepeng Pan commented on FLINK-39218:
-------------------------------------
Hi, [~savonitar]
Is the FLIP mainly related to FLINK main repo?
If so, Flink 2.4 will go into code freeze in mid-October. If this FLIP is
planned to be included in the 2.4 release, please help get it registered on the
[1] page. Thanks.
[1]
[https://cwiki.apache.org/confluence/spaces/FLINK/pages/449286596/2.4+Release]
Thanks!
> Introduce Flink-Kafka Transactions Management Tool
> --------------------------------------------------
>
> Key: FLINK-39218
> URL: https://issues.apache.org/jira/browse/FLINK-39218
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Reporter: Aleksandr Savonin
> Assignee: Aleksandr Savonin
> Priority: Major
> Labels: pull-request-available
>
> When a Flink job using the KafkaSink with EXACTLY_ONCE delivery guarantee
> stops unexpectedly (e.g., crash), it can leave Kafka transactions in an
> ONGOING state. These lingering transactions block downstream consumers
> operating in read_committed isolation level, as the Last Stable Offset (LSO)
> cannot advance past them.
> Currently, there is no built-in way to resolve this without restarting the
> original Flink job or waiting for the transaction timeout.
> This ticket adds a dedicated CLI tool
> (flink-connector-kafka-transaction-tool) packaged as a self-contained
> uber-jar that allows operators to manually resolve stuck transactions:
> * Abort: Connects with the same transactional.id to fence the previous
> producer, forcing the broker to abort the open transaction.
> * Commit: Resumes a specific transaction using the exact producerId and
> epoch from Flink checkpoint state/logs and commits it.
> The tool is implemented as a new Maven module
> (flink-connector-kafka-transaction-tool).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
