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

Posted to jira@kafka.apache.org by "Jose Armando Garcia Sancio (Jira)" <ji...@apache.org> on 2022/07/13 22:03:00 UTC

[jira] [Commented] (KAFKA-12473) Make the "cooperative-sticky, range" as the default assignor

    [ https://issues.apache.org/jira/browse/KAFKA-12473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17566509#comment-17566509 ] 

Jose Armando Garcia Sancio commented on KAFKA-12473:
----------------------------------------------------

[~ableegoldman] [~showuon] This KIP and issue is marked for the 3.3.0. I see that it is still unresolved. Do you want to keep it or remove it from the 3.3.0 release?

> Make the "cooperative-sticky, range" as the default assignor
> ------------------------------------------------------------
>
>                 Key: KAFKA-12473
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12473
>             Project: Kafka
>          Issue Type: Improvement
>          Components: consumer
>            Reporter: A. Sophie Blee-Goldman
>            Assignee: Luke Chen
>            Priority: Critical
>              Labels: kip
>             Fix For: 3.3.0
>
>
> Now that 3.0 is coming up, we can change the default ConsumerPartitionAssignor to something better than the RangeAssignor. The original plan was to switch over to the StickyAssignor, but now that we have incremental cooperative rebalancing we should  consider using the new CooperativeStickyAssignor instead: this will enable the consumer group to follow the COOPERATIVE protocol, improving the rebalancing experience OOTB.
> KIP: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177048248



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