[
https://issues.apache.org/jira/browse/KAFKA-18459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe updated KAFKA-18459:
---------------------------------
Description:
Eventually we will need to support multiple JDKs in ducktape.
One example of why we might want to do this is that we currently hack the older
releases to use a different ZK library than what they shipped with. We do this
because ZK 3.4 and earlier are not compatible with JDK 17 and newer. But this
is not the library the older Kafka release was actually released with, so this
setup may introduce subtle bugs (or maybe not, if we didn't use anything that
was removed in the newer ZK versions?)
Eventually there will probably be some breaking change in the JDK that will
require us to use historic JDKs for historic Kafka releases. For now, we're
hacking it to all use one new JDK.
was: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.
Priority: Major (was: Blocker)
Summary: Support multiple JDKs in ducktape (was: Use ZooKeeper 3.4 in
ducktape in order to support AK 2.1)
> Support multiple JDKs in ducktape
> ---------------------------------
>
> 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: Major
>
> Eventually we will need to support multiple JDKs in ducktape.
> One example of why we might want to do this is that we currently hack the
> older releases to use a different ZK library than what they shipped with. We
> do this because ZK 3.4 and earlier are not compatible with JDK 17 and newer.
> But this is not the library the older Kafka release was actually released
> with, so this setup may introduce subtle bugs (or maybe not, if we didn't use
> anything that was removed in the newer ZK versions?)
> Eventually there will probably be some breaking change in the JDK that will
> require us to use historic JDKs for historic Kafka releases. For now, we're
> hacking it to all use one new JDK.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
