[
https://issues.apache.org/jira/browse/KAFKA-18839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman updated KAFKA-18839:
-------------------------------------------
Description:
In 3.1 we deprecated the EAGER protocol in Kafka Streams (see KAFKA-13439).
This ticket covers actually dropping this protocol in 4.0.
Note that KAFKA-8575 covers the actual task cleanup we can do once we no longer
have to support eager rebalancing, which can now be done any time after 4.0
The effect of this will be that it is no longer be possible to perform a live
upgrade Kafka Streams directly to 4.0 from version 2.3 or below. Users will
have to go through a bridge release between 2.4 - 3.9 instead.
Note that several other incompatibilities that depend on the {{upgrade.from}}
config still remain, which require it to be used when upgrading from [2.4, 3.4]
to 3.5 or above. For this reason we recommend using a version in [3.5, 3.9] as
the bridge release, since this way you can still upgrade with only two rolling
bounces. To do so:
# apply the {{upgrade.from}} config in the first rolling bounce from 2.3-
to[3.5, 3.9]
# remove the {{upgrade.from}} config in the second rolling bounce which
upgrades to 4.0
was:
In 3.1 we deprecated the EAGER protocol in Kafka Streams (see KAFKA-13439).
This ticket covers actually dropping this protocol in 4.0.
Note that KAFKA-8575 covers the actual task cleanup we can do once we no longer
have to support eager rebalancing, which can now be done any time after 4.0
> Drop support for eager rebalancing in Streams
> ---------------------------------------------
>
> Key: KAFKA-18839
> URL: https://issues.apache.org/jira/browse/KAFKA-18839
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: A. Sophie Blee-Goldman
> Assignee: A. Sophie Blee-Goldman
> Priority: Major
> Fix For: 4.0.0
>
>
> In 3.1 we deprecated the EAGER protocol in Kafka Streams (see KAFKA-13439).
> This ticket covers actually dropping this protocol in 4.0.
> Note that KAFKA-8575 covers the actual task cleanup we can do once we no
> longer have to support eager rebalancing, which can now be done any time
> after 4.0
>
> The effect of this will be that it is no longer be possible to perform a live
> upgrade Kafka Streams directly to 4.0 from version 2.3 or below. Users will
> have to go through a bridge release between 2.4 - 3.9 instead.
> Note that several other incompatibilities that depend on the {{upgrade.from}}
> config still remain, which require it to be used when upgrading from [2.4,
> 3.4] to 3.5 or above. For this reason we recommend using a version in [3.5,
> 3.9] as the bridge release, since this way you can still upgrade with only
> two rolling bounces. To do so:
> # apply the {{upgrade.from}} config in the first rolling bounce from 2.3-
> to[3.5, 3.9]
> # remove the {{upgrade.from}} config in the second rolling bounce which
> upgrades to 4.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
