You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "James Cheng (Jira)" <ji...@apache.org> on 2020/09/23 03:40:00 UTC

[jira] [Assigned] (KAFKA-8653) Regression in JoinGroup v0 rebalance timeout handling

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

James Cheng reassigned KAFKA-8653:
----------------------------------

    Assignee: James Cheng  (was: Jason Gustafson)

> Regression in JoinGroup v0 rebalance timeout handling
> -----------------------------------------------------
>
>                 Key: KAFKA-8653
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8653
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>            Reporter: Jason Gustafson
>            Assignee: James Cheng
>            Priority: Blocker
>             Fix For: 2.3.1
>
>
> The rebalance timeout was added to the JoinGroup protocol in version 1. Prior to 2.3, we handled version 0 JoinGroup requests by setting the rebalance timeout to be equal to the session timeout. We lost this logic when we converted the API to use the generated schema definition which uses the default value of -1. The impact of this is that the group rebalance timeout becomes 0, so rebalances finish immediately after we enter the PrepareRebalance state and kick out all old members. This causes consumer groups to enter an endless rebalance loop.



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