[
https://issues.apache.org/jira/browse/KAFKA-14552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788593#comment-17788593
]
Ismael Juma commented on KAFKA-14552:
-------------------------------------
[~cmccabe] I noticed your work on
[KIP-1001|https://cwiki.apache.org/confluence/display/KAFKA/KIP-1001%3A+Some+New+Metrics+and+Config+Key+Deprecations].
Do you think it would make sense to include this in the same KIP or shall we
create a separate one?
> Remove no longer required server protocol versions in Kafka 4.0
> ---------------------------------------------------------------
>
> Key: KAFKA-14552
> URL: https://issues.apache.org/jira/browse/KAFKA-14552
> Project: Kafka
> Issue Type: Improvement
> Reporter: Ismael Juma
> Priority: Blocker
> Fix For: 4.0.0
>
>
> 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
> before 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).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
