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

Posted to jira@kafka.apache.org by "David Jacot (Jira)" <ji...@apache.org> on 2026/04/15 07:41:00 UTC

[jira] [Resolved] (KAFKA-20442) Consumer/Share/Streams group assignment epoch is not updated when the last member leaves

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

David Jacot resolved KAFKA-20442.
---------------------------------
    Fix Version/s: 4.4.0
       Resolution: Fixed

> Consumer/Share/Streams group assignment epoch is not updated when the last member leaves
> ----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-20442
>                 URL: https://issues.apache.org/jira/browse/KAFKA-20442
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 4.0.0, 4.1.0, 4.2.0, 4.3.0
>            Reporter: David Jacot
>            Assignee: David Jacot
>            Priority: Major
>             Fix For: 4.4.0
>
>
> When the last member of a consumer, share, or streams group leaves, the group epoch is bumped but no new target assignment is computed. This leaves the group in an inconsistent state where groupEpoch > assignmentEpocheven though the group is empty. The fix is to write a target assignment metadata record when the fence operation results in an empty group so that the assignment epoch catches up to the group epoch.



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