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

Posted to jira@kafka.apache.org by "Apoorv Mittal (Jira)" <ji...@apache.org> on 2025/12/02 15:49:00 UTC

[jira] [Resolved] (KAFKA-19953) Bug releasing acquired records when maintained on offset level

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

Apoorv Mittal resolved KAFKA-19953.
-----------------------------------
    Fix Version/s: 4.2.0
       Resolution: Fixed

> Bug releasing acquired records when maintained on offset level
> --------------------------------------------------------------
>
>                 Key: KAFKA-19953
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19953
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Abhinav Dixit
>            Assignee: Abhinav Dixit
>            Priority: Major
>             Fix For: 4.2.0
>
>
> When we have releaseAcquiredRecords call on SharePartition and the batch is being maintained per offset, if we have non matching member id while releasing acquired records, we should skip only that offset and continue with the next offset in the batch, not skip all the offsets after seeing the problematic offset
>  



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