Table of Contents |
---|
Status
Current state: "Under Discussion"
...
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
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.
...
As above table showed, since we already introduced a better assignor strategy, we should change the default assignor now.
Public Interfaces
With this KIP, the default value of partition.assignment.strategy
changes from "RangeAssignor"
to "CooperativeStickyAssignor"
- It won't affect to the current consumers
- New consumers with default
partition.assignment.strategy
will be affected - Upgrading the old consumer to the new consumer setting can refer to the following upgrade path section
Proposed Changes
- Change the default setting of
partition.assignment.strategy
in implementation and tests - When changing the default assignor we need to make sure this is clearly documented in the upgrade guide for 3.0
Compatibility, Upgrade path
this will require users to follow the upgrade path laid out in KIP-429 to safely perform a rolling upgrade:
<Copy from KIP-429>
From the user's perspective, the upgrade path of leveraging new protocols is similar to switching to a new assignor. For example, assuming the current version of Kafka consumer is 2.2 and "range" assignor is specified in the config (or no assignor is configured, which is identical as the RangeAssignor is the default below 3.0). The upgrade path would be:
...
The key point behind this two rolling bounce is that, we want to avoid the situation where leader is on old byte-code and only recognize "eager", but due to compatibility would still be able to deserialize the new protocol data from newer versioned members, and hence just go ahead and do the assignment while new versioned members did not revoke their partitions before joining the group. Note the difference with KIP-415 here: since on consumer we do not have the luxury to leverage on list of built-in assignors since it is user-customizable and hence would be black box to the consumer coordinator, we'd need two rolling bounces instead of one rolling bounce to complete the upgrade, whereas Connect only need one rolling bounce.
Rejected Alternatives
If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.