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

Posted to jira@kafka.apache.org by "Luke Chen (Jira)" <ji...@apache.org> on 2021/11/01 08:56:00 UTC

[jira] [Updated] (KAFKA-13420) consumer protocol should include "generation" field for assignor to distinguish between new/old OwnedPartitions

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

Luke Chen updated KAFKA-13420:
------------------------------
    Labels: need-kip  (was: )

> consumer protocol should include "generation" field for assignor to distinguish between new/old OwnedPartitions
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-13420
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13420
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients, consumer
>            Reporter: Luke Chen
>            Assignee: Luke Chen
>            Priority: Major
>              Labels: need-kip
>
> In [KIP-429|https://cwiki.apache.org/confluence/display/KAFKA/KIP-429%3A+Kafka+Consumer+Incremental+Rebalance+Protocol], we add a new field: `OwnedPartitions` into consumer protocol, for cooperative protocol do partition revoking things. But recently, we found the `ownedPartitions` info might be out-of-date due to some reasons (ex: unstable network), and the out-of-date  `ownedPartitions` causes unexpected rebalance stuck issue (ex: KAFKA-12984, KAFKA-13406). To fix it, we should consider to add the "generation" field in the consumer protocol, so that we can rely on the "generation" info to identify if the `ownedPartition` is up-to-date or out-of-date.



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