[
https://issues.apache.org/jira/browse/KAFKA-12473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman updated KAFKA-12473:
-------------------------------------------
Description:
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.
Note that this will require users to follow the [upgrade path laid out in
KIP-429|https://cwiki.apache.org/confluence/display/KAFKA/KIP-429:+Kafka+Consumer+Incremental+Rebalance+Protocol#KIP429:KafkaConsumerIncrementalRebalanceProtocol-Consumer]
to safely perform a rolling upgrade. When we change the default assignor we
need to make sure this is clearly documented in the upgrade guide for 3.0
was:
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.
Note that this will require users to follow the upgrade path laid out in
KIP-429 to safely perform a rolling upgrade. When we change the default
assignor we need to make sure this is clearly documented in the upgrade guide
for 3.0
> Make the CooperativeStickyAssignor 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: needs-kip
> Fix For: 3.0.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.
> Note that this will require users to follow the [upgrade path laid out in
> KIP-429|https://cwiki.apache.org/confluence/display/KAFKA/KIP-429:+Kafka+Consumer+Incremental+Rebalance+Protocol#KIP429:KafkaConsumerIncrementalRebalanceProtocol-Consumer]
> to safely perform a rolling upgrade. When we change the default assignor we
> need to make sure this is clearly documented in the upgrade guide for 3.0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
