[
https://issues.apache.org/jira/browse/KAFKA-18459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911631#comment-17911631
]
Chia-Ping Tsai commented on KAFKA-18459:
----------------------------------------
Please correct me if I misunderstand anything, but I run the
`client_compatibility_features_test.py` for broker LATEST_2_1 and it works
well.
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.
zk 3.5.x client are fully compatible with 3.9.x servers
(https://zookeeper.apache.org/releases.html), and in e2e ak 2.1 ~ 2.3 are using
zk 3.5.7 client (we replace 3.4.x manually
https://github.com/apache/kafka/blob/trunk/tests/docker/Dockerfile#L136).
Hence, in e2e ak 2.1 ~ 2.3 should work with newer versions of ZK-server
> 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)
