HOTFIX: cleanup bad cherry-pick

This commit is contained in:
Matthias J. Sax 2024-12-16 10:01:32 -08:00
parent bffe212b76
commit 6995e1e802
2 changed files with 0 additions and 24 deletions

View File

@ -137,7 +137,6 @@ versions += [
kafka_36: "3.6.2",
kafka_37: "3.7.2",
kafka_38: "3.8.1",
log4j2: "2.24.1",
// When updating lz4 make sure the compression levels in org.apache.kafka.common.record.CompressionType are still valid
lz4: "1.8.0",
mavenArtifact: "3.9.6",

View File

@ -167,29 +167,6 @@ chmod a+rw /opt/kafka-3.7.2
get_kafka 3.8.1 2.12
chmod a+rw /opt/kafka-3.8.1
# To ensure the Kafka cluster starts successfully under JDK 17, we need to update the Zookeeper
# client from version 3.4.x to 3.5.7 in Kafka versions 2.1.1, 2.2.2, and 2.3.1, as the older Zookeeper
# client is incompatible with JDK 17. See KAFKA-17888 for more details.
curl -s "https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.5.7/zookeeper-3.5.7.jar" -o /opt/zookeeper-3.5.7.jar
curl -s "https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper-jute/3.5.7/zookeeper-jute-3.5.7.jar" -o /opt/zookeeper-jute-3.5.7.jar
rm -f /opt/kafka-2.1.1/libs/zookeeper-*
rm -f /opt/kafka-2.2.2/libs/zookeeper-*
rm -f /opt/kafka-2.3.1/libs/zookeeper-*
cp /opt/zookeeper-3.5.7.jar /opt/kafka-2.1.1/libs/zookeeper-3.5.7.jar
chmod a+rw /opt/kafka-2.1.1/libs/zookeeper-3.5.7.jar
cp /opt/zookeeper-3.5.7.jar /opt/kafka-2.2.2/libs/zookeeper-3.5.7.jar
chmod a+rw /opt/kafka-2.2.2/libs/zookeeper-3.5.7.jar
cp /opt/zookeeper-3.5.7.jar /opt/kafka-2.3.1/libs/zookeeper-3.5.7.jar
chmod a+rw /opt/kafka-2.3.1/libs/zookeeper-3.5.7.jar
cp /opt/zookeeper-jute-3.5.7.jar /opt/kafka-2.1.1/libs/zookeeper-jute-3.5.7.jar
chmod a+rw /opt/kafka-2.1.1/libs/zookeeper-jute-3.5.7.jar
cp /opt/zookeeper-jute-3.5.7.jar /opt/kafka-2.2.2/libs/zookeeper-jute-3.5.7.jar
chmod a+rw /opt/kafka-2.2.2/libs/zookeeper-jute-3.5.7.jar
cp /opt/zookeeper-jute-3.5.7.jar /opt/kafka-2.3.1/libs/zookeeper-jute-3.5.7.jar
chmod a+rw /opt/kafka-2.3.1/libs/zookeeper-jute-3.5.7.jar
>>>>>>> 8c55dcc979 (KAFKA-18237: Upgrade system tests from using 3.7.1 to 3.7.2 (#18180))
# For EC2 nodes, we want to use /mnt, which should have the local disk. On local
# VMs, we can just create it if it doesn't exist and use it like we'd use
# /tmp. Eventually, we'd like to also support more directories, e.g. when EC2