Heya! I tested creating a cluster using the binary tgz. Furthermore, I went through the enabling, producing, consuming, and disabling of queues. Lastly, I carried out the same steps on both Docker images.
I went through the JavaDocs and clicked on links to confirm they work. I chose artifacts at random and confirmed that they are signed. I went through the release notes, and the OAuth jwt-bearer KIP is classified as an improvement and not as a new feature. I am uncertain whether we have a standardised way of differentiating between them and whether it is up to the KIP-implementer to correctly classify the JIRA ticket. Either way, I don’t think this is a blocker. I cross-checked the upgrade.html with what is currently on the kafka.apache.org website. It appears that in https://github.com/apache/kafka-site/blob/abd4e2ac9d4da0c7e3c54203925725c9e2da653d/41/upgrade.html (part of https://github.com/apache/kafka-site/pull/702/files) we have upgrade notes for 4.1.0, 4.0.0 and 3.9.0 while on the website we have upgrade notes for 4.0.0 and 3.9.0. I suspect we mention only the latest version and give a link to the previous one. In the latest PR, however, I believe we have 3 sections instead of just 2. It is a bit difficult to see whether the new addition to the default of group.coordinator.rebalance.protocols i.e. streams, is part of the documentation. Along the same lines, is the share value needed for the same configuration? There is no mention of it in https://cwiki.apache.org/confluence/display/KAFKA/Queues+for+Kafka+%28KIP-932%29+-+Preview+Release+Notes and I am able to produce and consume using the CLI tools without it? I don't feel that my documentation-related queries are a blocker. As such +1 (binding) for this release candidate from me :) Best, Christo On Wed, 30 Jul 2025 at 08:08, Paolo Patierno <paolo.patie...@gmail.com> wrote: > Of course, here my +1 (non binding) for the release :-) > > On Wed, 30 Jul 2025 at 08:15, Paolo Patierno <paolo.patie...@gmail.com> > wrote: > > > HI, > > within the Strimzi project we ran all the regression tests and everything > > seems to be fine. > > We had to deal with a behavioural change in Kafka 4.1. It seems that now > > ELR feature is enabled by default (while it was disabled in 4.0) and when > > it's enabled, you cannot change the min ISR broker configuration (but, if > > enabled, it was the same with 4.0). > > > > Thanks, > > Paolo Patierno > > > > On Mon, 28 Jul 2025 at 20:48, Mickael Maison <mickael.mai...@gmail.com> > > wrote: > > > >> Hi, > >> > >> Quick update about the system tests. > >> > >> Streams: > >> If I make the change suggested by Matthias, all the Streams tests pass. > >> So we need to update the release process to not run into this issue. > >> Either we don't only merge the RC tags into the release branch after > >> the vote, or we update the logic to not expect a SNAPSHOT version. > >> > >> Core: > >> While trying to debug > >> network_degrade_test.test_rate,name=rate-1000-latency-50, I noticed it > >> is also failing in my environment with 4.0.0. > >> Also the test was already flaky when introduced, see > >> https://github.com/apache/kafka/pull/18247#issuecomment-2550372486, so > >> I think we can consider not a blocker. > >> > >> Thanks, > >> Mickael > >> > >> On Sat, Jul 26, 2025 at 12:24 PM Andrew Schofield > >> <andrew_schofield_j...@outlook.com> wrote: > >> > > >> > Hi, > >> > I downloaded and tested 4.1.0 RC1. > >> > > >> > I successfully checked the enablement and administration of the share > >> > group and streams groups features. > >> > > >> > I also downloaded the documentation from the pending kafka-site PR. > >> > I observe that it was necessary to manually change the #include > >> > directives from 40 to 41 like this: > >> > > >> > <!--#include virtual="41/documentation.html" --> > >> > > >> > Once I'd done that, I could see the 4.1 documentation as expected. > >> > I guess that's part of the actual release process. > >> > > >> > Also checked the javadoc and that looks OK to me. > >> > > >> > +1 (non-binding) > >> > > >> > Thanks, > >> > Andrew > >> > > >> > ________________________________________ > >> > From: Kuan-Po Tseng <brandb...@gmail.com> > >> > Sent: 22 July 2025 16:43 > >> > To: dev@kafka.apache.org <dev@kafka.apache.org> > >> > Subject: Re: [VOTE] 4.1.0 RC1 > >> > > >> > Hi folks, > >> > > >> > I tested upgrading Kafka from both 3.7.2 and 3.8.1 to 4.1.0 and > >> everything > >> > seems good: > >> > - Three-node KRaft cluster; verified produce/consume records worked > >> > correctly using `kafka-producer-perf-test.sh` and > >> > `kafka-console-consumer.sh` before and after each server upgrade. > >> > - After upgrading one node to 4.1.0, saw repeated `The node does not > >> > support UPDATE_RAFT_VOTER` logs — expected since server with older > >> versions > >> > don't support this API. > >> > - Once all nodes were upgraded, the message disappeared. Everything > >> worked > >> > as expected. > >> > > >> > +1 (non-binding) > >> > > >> > Best, > >> > Kuan-Po Tseng > >> > > >> > On Tue, Jul 22, 2025 at 11:03 PM Chia-Ping Tsai <chia7...@gmail.com> > >> wrote: > >> > > >> > > hi > >> > > If anyone wants to test 4.1.0-RC1 without the backport fix, please > >> simply > >> > > configure the jdk_version to use another image. For example: > >> > > > >> > > jdk_version="openjdk:17-bullseye" /bin/bash > tests/docker/run_tests.sh > >> > > > >> > > Best, > >> > > Chia-Ping > >> > > > >> > > Josep Prat <josep.p...@aiven.io.invalid> 於 2025年7月22日 週二 下午10:56寫道： > >> > > > >> > > > Hi Mickael, > >> > > > I don't think we need a new RC just because of these files. > >> Technically > >> > > > speaking these files are part of the source tarball (which we > >> release), > >> > > but > >> > > > as they are test files, I wouldn't consider them as a blocker that > >> would > >> > > > grant a new RC. > >> > > > > >> > > > Best, > >> > > > > >> > > > On Tue, Jul 22, 2025 at 4:51 PM Mickael Maison < > >> mickael.mai...@gmail.com > >> > > > > >> > > > wrote: > >> > > > > >> > > > > Hi, > >> > > > > > >> > > > > Quick update regarding the system tests. My environment is back > >> but > >> > > > > now we're hitting > >> https://issues.apache.org/jira/browse/KAFKA-19501. > >> > > > > > >> > > > > Debian buster which is used in the system tests is out of > support > >> and > >> > > > > it's apt repository has now been archived. It worked till last > >> week > >> > > > > but now it's gone so we get an error when building the Docker > >> image. > >> > > > > We had only updated trunk to use bullseye. I've just backported > >> the > >> > > > > fix to 4.1: > >> > > > > > >> > > > > >> > > > >> > https://github.com/apache/kafka/commit/d5a3acda897890379edb8819f15b144fcea564b0 > >> > > > > > >> > > > > The fix is only in tests/docker/Dockerfile and > >> tests/docker/ducker-ak. > >> > > > > My understanding is that these files are not part of any of the > >> > > > > release artifacts. > >> > > > > So I'm considering keeping the RC1 artifacts and running the > >> system > >> > > > > tests with the fix. > >> > > > > > >> > > > > Let me know if my understand is incorrect, or if you'd prefer > >> building > >> > > > > a new RC regardless. Obviously if we find issues with RC1, we'll > >> do > >> > > > > another RC anyway. > >> > > > > > >> > > > > Thanks, > >> > > > > Mickael > >> > > > > > >> > > > > > >> > > > > > >> > > > > On Mon, Jul 21, 2025 at 5:04 PM Mickael Maison < > >> > > mickael.mai...@gmail.com > >> > > > > > >> > > > > wrote: > >> > > > > > > >> > > > > > Hello Kafka users, developers and client-developers, > >> > > > > > > >> > > > > > This is the second candidate for release of Apache Kafka > 4.1.0. > >> > > > > > > >> > > > > > The release brings many new features and improvements: > >> > > > > > - Mechanism for plugin to register metrics > >> > > > > > - Allow running multiple versions of connector plugins > >> > > > > > - Queue are now in preview access > >> > > > > > - New Streams rebalance protocol in early access > >> > > > > > - Support for OAuth jwt-bearer grant type > >> > > > > > - Improved metadata replication > >> > > > > > > >> > > > > > Release notes for the 4.1.0 release: > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > https://dist.apache.org/repos/dist/dev/kafka/4.1.0-rc1/RELEASE_NOTES.html > >> > > > > > > >> > > > > > *** Please download, test and vote by Friday July 25. > >> > > > > > > >> > > > > > 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://dist.apache.org/repos/dist/dev/kafka/4.1.0-rc1/ > >> > > > > > > >> > > > > > * Docker release artifacts to be voted upon: > >> > > > > > apache/kafka:4.1.0-rc1 > >> > > > > > apache/kafka-native:4.1.0-rc1 > >> > > > > > > >> > > > > > * Maven artifacts to be voted upon: > >> > > > > > > >> > > > >> https://repository.apache.org/content/groups/staging/org/apache/kafka/ > >> > > > > > > >> > > > > > * Javadoc: > >> > > > > > > https://dist.apache.org/repos/dist/dev/kafka/4.1.0-rc1/javadoc/ > >> > > > > > > >> > > > > > * Tag to be voted upon (off 4.1 branch) is the 4.1.0 tag: > >> > > > > > https://github.com/apache/kafka/releases/tag/4.1.0-rc1 > >> > > > > > > >> > > > > > * Documentation: > >> > > > > > https://kafka.apache.org/41/documentation.html > >> > > > > > PR (https://github.com/apache/kafka-site/pull/702) is not > >> merged yet > >> > > > > > > >> > > > > > * Protocol: > >> > > > > > https://kafka.apache.org/41/protocol.html > >> > > > > > PR (https://github.com/apache/kafka-site/pull/702) is not > >> merged yet > >> > > > > > > >> > > > > > * Successful CI builds for the 4.1 branch: > >> > > > > > Unit/integration tests: > >> > > > > https://github.com/apache/kafka/actions/runs/16415760777 > >> > > > > > System tests: The environment I use for running the system > >> tests is > >> > > > > > under maintenance. If someone can run the system tests, go > >> ahead. > >> > > > > > Otherwise I'll send an update once I'm able to run them. > >> > > > > > > >> > > > > > * Successful Docker Image Github Actions Pipeline for 4.1 > >> branch: > >> > > > > > Docker Build Test Pipeline (JVM): > >> > > > > > https://github.com/apache/kafka/actions/runs/16415783067 > >> > > > > > Docker Build Test Pipeline (Native): > >> > > > > > https://github.com/apache/kafka/actions/runs/16415786103 > >> > > > > > > >> > > > > > Thanks, > >> > > > > > Mickael > >> > > > > > >> > > > > >> > > > > >> > > > -- > >> > > > [image: Aiven] <https://www.aiven.io/> > >> > > > > >> > > > *Josep Prat* > >> > > > Sr. Engineering Director, Streaming Services, *Aiven* > >> > > > josep.p...@aiven.io | +491715557497 > >> > > > aiven.io <https://www.aiven.io/> | < > >> > > https://www.facebook.com/aivencloud > >> > > > > > >> > > > <https://www.linkedin.com/company/aiven/> < > >> > > > https://twitter.com/aiven_io> > >> > > > *Aiven Deutschland GmbH* > >> > > > Alexanderufer 3-7, 10117 Berlin > >> > > > > >> > > > Geschäftsführer: Oskari Saarenmaa, Hannu Valtonen, > >> > > > > >> > > > Kenneth Chen > >> > > > Amtsgericht Charlottenburg, HRB 209739 B > >> > > > > >> > > > >> > > > > > > -- > > Paolo Patierno > > > > *Senior Principal Software Engineer @ IBM**CNCF Ambassador* > > > > Twitter : @ppatierno <http://twitter.com/ppatierno> > > Linkedin : paolopatierno <http://it.linkedin.com/in/paolopatierno> > > GitHub : ppatierno <https://github.com/ppatierno> > > > > > -- > Paolo Patierno > > *Senior Principal Software Engineer @ IBM**CNCF Ambassador* > > Twitter : @ppatierno <http://twitter.com/ppatierno> > Linkedin : paolopatierno <http://it.linkedin.com/in/paolopatierno> > GitHub : ppatierno <https://github.com/ppatierno> >
