[
https://issues.apache.org/jira/browse/KAFKA-14552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-14552:
--------------------------------
Description:
Kafka 4.0 will remove support for zk mode and will require conversion to kraft
before upgrading to 4.0. The minimum kraft version is 3.0 (aka 3.0-IV1).
This provides an opportunity to remove exclusively server side protocols
versions that only exist to allow direct upgrades from versions older than 3.0
or that are used only by zk mode.
Since KRaft became production ready in 3.3, we should consider setting the
baseline to 3.3. But that requires more discussion and it can be done via a
separate change.
was:
Kafka 4.0 will remove support for zk mode and kraft mode became production
ready in Kafka 3.3. Furthermore, migration from zk mode to kraft mode will
require upgrading to the bridge release first (likely 3.5, but could also be
3.6).
This provides an opportunity to remove exclusively server side protocols
versions that only exist to allow direct upgrades from versions older than 3.n
where n is either 0 (KRaft preview), 3 (KRaft production ready) or 5 (bridge
release). We should decide on the right `n` and make the change as part of 4.0.
Note that this is complementary to the protocols that will be completely
removed as part of zk mode removal. Step one would be to create a list of
protocols that will be completely removed due to zk mode removal and the list
of exclusively server side protocols remaining after that (one example is
ControlledShutdown).
> Assume a baseline of 3.0 for server protocol versions
> -----------------------------------------------------
>
> Key: KAFKA-14552
> URL: https://issues.apache.org/jira/browse/KAFKA-14552
> Project: Kafka
> Issue Type: Improvement
> Reporter: Ismael Juma
> Assignee: Ismael Juma
> Priority: Blocker
> Fix For: 4.0.0
>
>
> Kafka 4.0 will remove support for zk mode and will require conversion to
> kraft before upgrading to 4.0. The minimum kraft version is 3.0 (aka 3.0-IV1).
> This provides an opportunity to remove exclusively server side protocols
> versions that only exist to allow direct upgrades from versions older than
> 3.0 or that are used only by zk mode.
> Since KRaft became production ready in 3.3, we should consider setting the
> baseline to 3.3. But that requires more discussion and it can be done via a
> separate change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
