[
https://issues.apache.org/jira/browse/KAFKA-18459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923539#comment-17923539
]
Colin McCabe commented on KAFKA-18459:
--------------------------------------
[~chia7712] thanks for commenting. I wasn't aware that we were replacing the ZK
3.4 jars with ZK 3.5 ones by using rm and cp. That's a bit risky, as I'm sure
you know. However, if it is working for now, then maybe we don't have to change
anything for the AK 4.0 release.
I do think eventually we will need to run the older releases with their
"historic JDKs" but if we can put off doing that for now, that's fine.
> You have mentioned that "ZK 3.5.7 is not compatible with Kafka 2.1 Please
> read KIP-902"
> (https://github.com/apache/kafka/pull/17576#issuecomment-2452655129), but I
> failed to get your point.
Looking at the chart again, I think I mis-spoke. ZK 3.5 is compatible with
Kafka 2.1 although it didn't ship with that release. It's ZK 3.8 that has the
incompatibility.
I will mark this as not a blocker if the tests are passing with this setup.
Thanks for the corrections.
> Use ZooKeeper 3.4 in ducktape in order to support AK 2.1
> --------------------------------------------------------
>
> Key: KAFKA-18459
> URL: https://issues.apache.org/jira/browse/KAFKA-18459
> Project: Kafka
> Issue Type: Sub-task
> Affects Versions: 4.0.0
> Reporter: Colin McCabe
> Priority: Blocker
>
> We have to support AK 2.1 in our ducktape tests. This version of AK is
> ZK-only (no kraft support) and does not support newer versions of ZK. So we
> should switch our ducktape code to only use ZK 3.4, since that supports the
> old AK that we've committed to support.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
