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

Posted to dev@kafka.apache.org by "Justine Olshan (Jira)" <ji...@apache.org> on 2025/01/28 18:36:00 UTC

[jira] [Resolved] (KAFKA-18661) Transactions Version 2 doesn't handle epoch overflow correctly

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

Justine Olshan resolved KAFKA-18661.
------------------------------------
    Resolution: Duplicate

Jira was spinning and created this twice.

> Transactions Version 2 doesn't handle epoch overflow correctly
> --------------------------------------------------------------
>
>                 Key: KAFKA-18661
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18661
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 4.0.0
>            Reporter: Justine Olshan
>            Assignee: Justine Olshan
>            Priority: Blocker
>
> We should be returning the new epoch and producer ID to the client so we should be using newPreSendMetadata here. [https://github.com/apache/kafka/blob/f18457f2b8f7adc5fb8ea2c46dcf38973aaf4667/core/src/main/scala/kafka/coordinator/transaction/TransactionCoordinator.scala#L943]
> However, when testing this change I found some of the old producer id + epoch causing issues – likely because we haven't transitioned to the new metadata (ie concurrent transactions issue), so we will need to handle that as well. 



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