I did the following release validations - - Verified that `./gradlew test` is successful on an ARM machine - Verified that we are able to scrape metrics from JMX port - Verified that a cluster running two brokers, 3.3.2 and 3.3.1 respectively, produce/consume works for both Zk and kraft
Will wait for system test results before adding +1 vote. *Minor concerns (not release blockers):* When I try to create a __cluster_metadata topic, it fails with the expected Authorization failed but prints a weird log line with a date (see last line below) $ kafka-topics.sh --create --replication-factor 1 --partitions 1 --topic __cluster_metadata --bootstrap-server <broker-endpoint>:9092 SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/opt/kafka/tools/build/dependant-libs-2.13.8/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/opt/kafka/connect/runtime/build/dependant-libs/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.slf4j.impl.Reload4jLoggerFactory] WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both. Error while executing topic command : Authorization failed. [2022-12-22 12:45:36,242] ERROR org.apache.kafka.common.errors.TopicAuthorizationException: Authorization failed. (kafka.admin.TopicCommand$) -- Divij Vaidya On Thu, Dec 22, 2022 at 7:12 AM Yash Mayya <yash.ma...@gmail.com> wrote: > Hi Chris, > > I did the following release validations - > > - Verified the MD5 / SHA-1 / SHA-512 checksums and the PGP signatures > - Built from source using Java 8 and Scala 2.13 > - Ran all the unit tests successfully > - Ran all the integration tests successfully (couple of flaky failures that > passed on a rerun - `TopicCommandIntegrationTest. > testDeleteInternalTopic(String).quorum=kraft` and > `SaslScramSslEndToEndAuthorizationTest. > testNoConsumeWithoutDescribeAclViaSubscribe()`) > - Quickstart for Kafka and Kafka Connect with both ZooKeeper and KRaft > > I'm +1 (non-binding) assuming that the system test results look good. > > Thanks, > Yash > > On Thu, Dec 22, 2022 at 3:52 AM Chris Egerton <chr...@aiven.io.invalid> > wrote: > > > Hello Kafka users, developers and client-developers, > > > > This is the second candidate for release of Apache Kafka 3.3.2. > > > > This is a bugfix release with several fixes since the release of 3.3.1. A > > few of the major issues include: > > > > * KAFKA-14358 Users should not be able to create a regular topic name > > __cluster_metadata > > KAFKA-14379 Consumer should refresh preferred read replica on update > > metadata > > * KAFKA-13586 Prevent exception thrown during connector update from > > crashing distributed herder > > > > > > Release notes for the 3.3.2 release: > > https://home.apache.org/~cegerton/kafka-3.3.2-rc1/RELEASE_NOTES.html > > > > *** Please download, test and vote by Friday, January 6, 2023, 10pm UTC > > (this date is chosen to accommodate the various upcoming holidays that > > members of the community will be taking and give everyone enough time to > > test out the release candidate, without unduly delaying the release) > > > > Kafka's KEYS file containing PGP keys we use to sign the release: > > https://kafka.apache.org/KEYS > > > > * Release artifacts to be voted upon (source and binary): > > https://home.apache.org/~cegerton/kafka-3.3.2-rc1/ > > > > * Maven artifacts to be voted upon: > > https://repository.apache.org/content/groups/staging/org/apache/kafka/ > > > > * Javadoc: > > https://home.apache.org/~cegerton/kafka-3.3.2-rc1/javadoc/ > > > > * Tag to be voted upon (off 3.3 branch) is the 3.3.2 tag: > > https://github.com/apache/kafka/releases/tag/3.3.2-rc1 > > > > * Documentation: > > https://kafka.apache.org/33/documentation.html > > > > * Protocol: > > https://kafka.apache.org/33/protocol.html > > > > The most recent build has had test failures. These all appear to be due > to > > flakiness, but it would be nice if someone more familiar with the failed > > tests could confirm this. I may update this thread with passing build > links > > if I can get one, or start a new release vote thread if test failures > must > > be addressed beyond re-running builds until they pass. > > > > Unit/integration tests: > > https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.3/142/testReport/ > > > > José, would it be possible to re-run the system tests for 3.3 on the > latest > > commit for 3.3 (e3212f2), and share the results on this thread? > > > > Cheers, > > > > Chris > > >
