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

Posted to jira@kafka.apache.org by "Justine Olshan (Jira)" <ji...@apache.org> on 2026/10/21 22:54:00 UTC

[jira] [Updated] (KAFKA-20734) Offline partition can cause loss of transaction markers

     [ https://issues.apache.org/jira/browse/KAFKA-20734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justine Olshan updated KAFKA-20734:
-----------------------------------
    Affects Version/s: 4.5
                       4.4.0

> 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
(v8.20.10#820010)