[jira] [Resolved] (KAFKA-15967) Fix revocation in reconcilation logic

["Lianet Magrans (Jira)" <ji...@apache.org>]

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

Lianet Magrans resolved KAFKA-15967.
------------------------------------
    Fix Version/s: 3.7.0
                       (was: 3.8.0)
         Assignee: Lianet Magrans
       Resolution: Fixed

> Fix revocation in reconcilation logic
> -------------------------------------
>
>                 Key: KAFKA-15967
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15967
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer
>            Reporter: Lucas Brutschy
>            Assignee: Lianet Magrans
>            Priority: Major
>              Labels: kip-848, kip-848-client-support
>             Fix For: 3.7.0
>
>
> Looks like there is a problem in the reconciliation logic.
> We are getting 6 partitions from an HB, we add them to {{{}assignmentReadyToReconcile{}}}. Next HB we get only 4 partitions (2 are revoked), we also add them to {{{}assignmentReadyToReconcile{}}}, but the 2 partitions that were supposed to be removed from the assignment are never removed because they are still in {{{}assignmentReadyToReconcile{}}}.
> This was discovered during integration testing of [https://github.com/apache/kafka/pull/14878] - part of the test testRemoteAssignorRange was disabled and should be re-enabled once this is fixed.



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