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

Posted to dev@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2021/08/24 19:06:00 UTC

[jira] [Resolved] (KAFKA-13214) Consumer should not reset group state after disconnect

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

Jason Gustafson resolved KAFKA-13214.
-------------------------------------
    Fix Version/s: 2.8.1
                   2.7.2
                   3.0.0
       Resolution: Fixed

> Consumer should not reset group state after disconnect
> ------------------------------------------------------
>
>                 Key: KAFKA-13214
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13214
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 2.7.0, 2.8.0
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Critical
>             Fix For: 3.0.0, 2.7.2, 2.8.1
>
>
> When the consumer disconnects from the coordinator while a rebalance is in progress, we currently reset the memberId and generation. The coordinator then must await the session timeout in order to expire the old memberId. This was apparently a regression from https://github.com/apache/kafka/commit/7e7bb184d2abe34280a7f0eb0f0d9fc0e32389f2#diff-15efe9b844f78b686393b6c2e2ad61306c3473225742caed05c7edab9a138832R478. It would be better to keep the memberId/generation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)