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

Posted to dev@kafka.apache.org by "Lianet Magrans (Jira)" <ji...@apache.org> on 2024/03/25 14:11:00 UTC

[jira] [Resolved] (KAFKA-16375) Fix logic for discarding reconciliation if member rejoined

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

Lianet Magrans resolved KAFKA-16375.
------------------------------------
    Resolution: Fixed

> Fix logic for discarding reconciliation if member rejoined
> ----------------------------------------------------------
>
>                 Key: KAFKA-16375
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16375
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, consumer
>            Reporter: Lianet Magrans
>            Assignee: Lianet Magrans
>            Priority: Critical
>              Labels: client-transitions-issues, kip-848-client-support
>             Fix For: 3.8.0
>
>
> The current implementation of the new consumer discards the result of a reconciliation if the member rejoined, based on a comparison of the member epoch at the start and end of the reconciliation. If the epochs changed the reconciliation is discarded. This is not right because the member epoch could be incremented without an assignment change. This should be fixed to ensure that the reconciliation is discarded if the member rejoined, probably based on a flag that truly reflects that it went through a transition to joining while reconciling.



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