[
https://issues.apache.org/jira/browse/KAFKA-20734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133642#comment-18133642
]
Philipp Schirmer commented on KAFKA-20734:
------------------------------------------
Apparently PRs have been merged for this. Is there already a timeline for
releasing this? Either as 4.3.3 or 4.4.1? Because this is kinda blocking our
Kafka setup
> Offline partition can cause loss of transaction markers
> -------------------------------------------------------
>
> Key: KAFKA-20734
> URL: https://issues.apache.org/jira/browse/KAFKA-20734
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 4.3.0, 4.4.0, 4.5
> Reporter: Alyssa Huang
> Assignee: Wang Xiaoqing
> Priority: Blocker
>
> During the rewrite of the KRaftMetadataCache (as part of KAFKA-17573), a bug
> was introduced which causes transaction coordinator to drop transaction
> markers for a partition if the leader is missing (offline). Specifically,
> {{metadataCache.getPartitionLeaderEndpoint}} returns {{None}} instead of
> {{Some(Node.noNode).}}
> This bug can cause hanging transaction and lost commit markers. Thanks
> [~alivshits] for the identification of this issue.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
