You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by Mickael Maison <mi...@gmail.com> on 2025/07/21 15:04:23 UTC

[VOTE] 4.1.0 RC1

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

Re: [VOTE] 4.1.0 RC1

Posted by Chia-Ping Tsai <ch...@apache.org>.

I've opened https://issues.apache.org/jira/browse/KAFKA-20085 to ensure we worker smarter rather than harder.

On 2025/07/25 15:42:35 Mickael Maison wrote:
> Hi,
> 
> Here are the system tests results:
> https://drive.google.com/file/d/1wXSuwBKNWrmq1BQzfoC7B2Qelj91P2ih/view?usp=sharing
> 
> Like in RC0, these following test is consistently failing in my environment:
> kafkatest.tests.core.network_degrade_test.test_rate_device_name=eth0_latency_ms=50_metadata_quorum=COMBINED_KRAFT_rate_limit_kbit=1000000_task_name=rate-1000-latency-50
> I opened https://issues.apache.org/jira/browse/KAFKA-19549. Can
> someone else try to run that test in their environment?
> 
> All the Streams upgrade system tests to 4.1.0 also failed with the
> following error: "Could not detect Kafka Streams version
> 4.1.0-SNAPSHOT.".
> This is probably due to the fact that the release script now merges
> the release tag (4.1.0-rc1) into the release branch (4.1), so the
> branch has 4.1.0 as its version.
> It would be good is Streams people could take a look.
> 
> Thanks,
> Mickael
> 
> 
> 
> On Tue, Jul 22, 2025 at 5:44 PM Kuan-Po Tseng <br...@gmail.com> wrote:
> >
> > 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 <ch...@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 <jo...@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.maison@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.maison@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.prat@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
> > > >
> > >
>

Re: [VOTE] 4.1.0 RC1

Posted by "Matthias J. Sax" <mj...@apache.org>.

> "Could not detect Kafka Streams version
>> 4.1.0-SNAPSHOT.".

We get this version from 
https://github.com/apache/kafka/blob/4.1/tests/kafkatest/version.py#L113

kafka/tests/kafkatest/version.py

> DEV_VERSION = KafkaVersion("4.1.0-SNAPSHOT")


Does this help to fix it? Do you plan to take it on? Or do you need help 
from our side?


-Matthias


On 7/25/25 8:42 AM, Mickael Maison wrote:
> Hi,
> 
> Here are the system tests results:
> https://drive.google.com/file/d/1wXSuwBKNWrmq1BQzfoC7B2Qelj91P2ih/view?usp=sharing
> 
> Like in RC0, these following test is consistently failing in my environment:
> kafkatest.tests.core.network_degrade_test.test_rate_device_name=eth0_latency_ms=50_metadata_quorum=COMBINED_KRAFT_rate_limit_kbit=1000000_task_name=rate-1000-latency-50
> I opened https://issues.apache.org/jira/browse/KAFKA-19549. Can
> someone else try to run that test in their environment?
> 
> All the Streams upgrade system tests to 4.1.0 also failed with the
> following error: "Could not detect Kafka Streams version
> 4.1.0-SNAPSHOT.".
> This is probably due to the fact that the release script now merges
> the release tag (4.1.0-rc1) into the release branch (4.1), so the
> branch has 4.1.0 as its version.
> It would be good is Streams people could take a look.
> 
> Thanks,
> Mickael
> 
> 
> 
> On Tue, Jul 22, 2025 at 5:44 PM Kuan-Po Tseng <br...@gmail.com> wrote:
>>
>> 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 <ch...@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 <jo...@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.maison@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.maison@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.prat@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
>>>>
>>>

Re: [VOTE] 4.1.0 RC1

Posted by Federico Valeri <fe...@gmail.com>.

Hi Mickael, I can confirm that
network_degrade_test.test_rate,name=rate-1000-latency-50 fails
constantly with the error you reported.

On Fri, Jul 25, 2025 at 5:43 PM Mickael Maison <mi...@gmail.com> wrote:
>
> Hi,
>
> Here are the system tests results:
> https://drive.google.com/file/d/1wXSuwBKNWrmq1BQzfoC7B2Qelj91P2ih/view?usp=sharing
>
> Like in RC0, these following test is consistently failing in my environment:
> kafkatest.tests.core.network_degrade_test.test_rate_device_name=eth0_latency_ms=50_metadata_quorum=COMBINED_KRAFT_rate_limit_kbit=1000000_task_name=rate-1000-latency-50
> I opened https://issues.apache.org/jira/browse/KAFKA-19549. Can
> someone else try to run that test in their environment?
>
> All the Streams upgrade system tests to 4.1.0 also failed with the
> following error: "Could not detect Kafka Streams version
> 4.1.0-SNAPSHOT.".
> This is probably due to the fact that the release script now merges
> the release tag (4.1.0-rc1) into the release branch (4.1), so the
> branch has 4.1.0 as its version.
> It would be good is Streams people could take a look.
>
> Thanks,
> Mickael
>
>
>
> On Tue, Jul 22, 2025 at 5:44 PM Kuan-Po Tseng <br...@gmail.com> wrote:
> >
> > 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 <ch...@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 <jo...@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.maison@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.maison@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.prat@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
> > > >
> > >

Re: [VOTE] 4.1.0 RC1

Posted by Mickael Maison <mi...@gmail.com>.

Hi,

Here are the system tests results:
https://drive.google.com/file/d/1wXSuwBKNWrmq1BQzfoC7B2Qelj91P2ih/view?usp=sharing

Like in RC0, these following test is consistently failing in my environment:
kafkatest.tests.core.network_degrade_test.test_rate_device_name=eth0_latency_ms=50_metadata_quorum=COMBINED_KRAFT_rate_limit_kbit=1000000_task_name=rate-1000-latency-50
I opened https://issues.apache.org/jira/browse/KAFKA-19549. Can
someone else try to run that test in their environment?

All the Streams upgrade system tests to 4.1.0 also failed with the
following error: "Could not detect Kafka Streams version
4.1.0-SNAPSHOT.".
This is probably due to the fact that the release script now merges
the release tag (4.1.0-rc1) into the release branch (4.1), so the
branch has 4.1.0 as its version.
It would be good is Streams people could take a look.

Thanks,
Mickael



On Tue, Jul 22, 2025 at 5:44 PM Kuan-Po Tseng <br...@gmail.com> wrote:
>
> 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 <ch...@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 <jo...@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.maison@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.maison@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.prat@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
> > >
> >

Re: [VOTE] 4.1.0 RC1

Posted by Mickael Maison <mi...@gmail.com>.

Hi Luke,

Thanks for the heads up.
I replied in the PR associated with the discussion. I'll copy my reply
here too so everyone is aware:

I think it's fine to merge this as this renaming was accidental and
unwanted. However we should probably add a note in notable changes in
4.0.0 to indicate the name has changed.
I'm also happy to have this backported to 4.1, with also a note in the
4.1 notable changes indicating this mistake has been fixed

This will require doing another RC, so we'll be able to pick up the
few doc changes we were working on in parallel of the release.

So closing this vote, I'll start working on another RC once these PRs
are merged.

Thanks,
Mickael

On Mon, Aug 4, 2025 at 4:29 AM Luke Chen <sh...@gmail.com> wrote:
>
> Hi Mickael,
>
> Could you take a look at this issue, and see if we want to include this
> patch into v4.1.0?
> https://lists.apache.org/thread/83kqzk823xcxfj5w2t68sdftmo7t0bpz
>
> Thank you.
> Luke
>
> On Sat, Aug 2, 2025 at 1:50 AM Jun Rao <ju...@confluent.io.invalid> wrote:
>
> > I chatted with Andrew Schofield. So, share is not required in
> > group.coordinator.rebalance.protocols to enable share consumers. One just
> > needs to set share.version.
> >
> > Thanks,
> >
> > Jun
> >
> > On Fri, Aug 1, 2025 at 6:09 AM Paolo Patierno <pa...@gmail.com>
> > wrote:
> >
> > > Hi Jun,
> > > yes I think it's clearer now. Thanks.
> > >
> > > Paolo
> > >
> > > On Thu, 31 Jul 2025 at 22:31, Jun Rao <ju...@confluent.io.invalid> wrote:
> > >
> > > > Hi, Paolo,
> > > >
> > > > Thanks for the context. Do you feel that the doc change addresses your
> > > > concern?
> > > >
> > > > Jun
> > > >
> > > > On Thu, Jul 31, 2025 at 5:13 AM Paolo Patierno <
> > paolo.patierno@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Hi Jun,
> > > > > thanks ... that PR came after a long discussion we had in the Strimzi
> > > > > community
> > > https://github.com/strimzi/strimzi-kafka-operator/issues/11685
> > > > > when found out about this behaviour ;-)
> > > > >
> > > > > Thanks,
> > > > > Paolo
> > > > >
> > > > > On Wed, 30 Jul 2025 at 18:55, Jun Rao <ju...@confluent.io.invalid>
> > > wrote:
> > > > >
> > > > > > Hi, Paolo,
> > > > > >
> > > > > > There is a PR https://github.com/apache/kafka/pull/20268 for the
> > doc
> > > > > > change
> > > > > > for ELR.
> > > > > >
> > > > > > Hi, Christo,
> > > > > >
> > > > > > Group rebalance is designed so that each partition is only consumed
> > > by
> > > > a
> > > > > > single consumer instance at a time. Share consumer by design
> > allows a
> > > > > > single partition to be consumed by more than one consumer at any
> > > time.
> > > > > So,
> > > > > > it doesn't need group.coordinator.rebalance.protocols.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Jun
> > > > > >
> > > > > > On Wed, Jul 30, 2025 at 6:14 AM Christo Lolov <
> > > christololov@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > 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.patierno@gmail.com
> > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Of course, here my +1 (non binding) for the release :-)
> > > > > > > >
> > > > > > > > On Wed, 30 Jul 2025 at 08:15, Paolo Patierno <
> > > > > paolo.patierno@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.maison@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
> > > > > > > > >> <an...@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 <br...@gmail.com>
> > > > > > > > >> > Sent: 22 July 2025 16:43
> > > > > > > > >> > To: dev@kafka.apache.org <de...@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 <
> > > > > > chia7712@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 <jo...@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.maison@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.maison@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.prat@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>
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > 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>
> > >
> >

Re: [VOTE] 4.1.0 RC1

Posted by Luke Chen <sh...@gmail.com>.

Hi Mickael,

Could you take a look at this issue, and see if we want to include this
patch into v4.1.0?
https://lists.apache.org/thread/83kqzk823xcxfj5w2t68sdftmo7t0bpz

Thank you.
Luke

On Sat, Aug 2, 2025 at 1:50 AM Jun Rao <ju...@confluent.io.invalid> wrote:

> I chatted with Andrew Schofield. So, share is not required in
> group.coordinator.rebalance.protocols to enable share consumers. One just
> needs to set share.version.
>
> Thanks,
>
> Jun
>
> On Fri, Aug 1, 2025 at 6:09 AM Paolo Patierno <pa...@gmail.com>
> wrote:
>
> > Hi Jun,
> > yes I think it's clearer now. Thanks.
> >
> > Paolo
> >
> > On Thu, 31 Jul 2025 at 22:31, Jun Rao <ju...@confluent.io.invalid> wrote:
> >
> > > Hi, Paolo,
> > >
> > > Thanks for the context. Do you feel that the doc change addresses your
> > > concern?
> > >
> > > Jun
> > >
> > > On Thu, Jul 31, 2025 at 5:13 AM Paolo Patierno <
> paolo.patierno@gmail.com
> > >
> > > wrote:
> > >
> > > > Hi Jun,
> > > > thanks ... that PR came after a long discussion we had in the Strimzi
> > > > community
> > https://github.com/strimzi/strimzi-kafka-operator/issues/11685
> > > > when found out about this behaviour ;-)
> > > >
> > > > Thanks,
> > > > Paolo
> > > >
> > > > On Wed, 30 Jul 2025 at 18:55, Jun Rao <ju...@confluent.io.invalid>
> > wrote:
> > > >
> > > > > Hi, Paolo,
> > > > >
> > > > > There is a PR https://github.com/apache/kafka/pull/20268 for the
> doc
> > > > > change
> > > > > for ELR.
> > > > >
> > > > > Hi, Christo,
> > > > >
> > > > > Group rebalance is designed so that each partition is only consumed
> > by
> > > a
> > > > > single consumer instance at a time. Share consumer by design
> allows a
> > > > > single partition to be consumed by more than one consumer at any
> > time.
> > > > So,
> > > > > it doesn't need group.coordinator.rebalance.protocols.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Jun
> > > > >
> > > > > On Wed, Jul 30, 2025 at 6:14 AM Christo Lolov <
> > christololov@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > 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.patierno@gmail.com
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Of course, here my +1 (non binding) for the release :-)
> > > > > > >
> > > > > > > On Wed, 30 Jul 2025 at 08:15, Paolo Patierno <
> > > > paolo.patierno@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.maison@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
> > > > > > > >> <an...@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 <br...@gmail.com>
> > > > > > > >> > Sent: 22 July 2025 16:43
> > > > > > > >> > To: dev@kafka.apache.org <de...@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 <
> > > > > chia7712@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 <jo...@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.maison@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.maison@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.prat@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>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > 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>
> >
>

Re: [VOTE] 4.1.0 RC1

Posted by Jun Rao <ju...@confluent.io.INVALID>.

I chatted with Andrew Schofield. So, share is not required in
group.coordinator.rebalance.protocols to enable share consumers. One just
needs to set share.version.

Thanks,

Jun

On Fri, Aug 1, 2025 at 6:09 AM Paolo Patierno <pa...@gmail.com>
wrote:

> Hi Jun,
> yes I think it's clearer now. Thanks.
>
> Paolo
>
> On Thu, 31 Jul 2025 at 22:31, Jun Rao <ju...@confluent.io.invalid> wrote:
>
> > Hi, Paolo,
> >
> > Thanks for the context. Do you feel that the doc change addresses your
> > concern?
> >
> > Jun
> >
> > On Thu, Jul 31, 2025 at 5:13 AM Paolo Patierno <paolo.patierno@gmail.com
> >
> > wrote:
> >
> > > Hi Jun,
> > > thanks ... that PR came after a long discussion we had in the Strimzi
> > > community
> https://github.com/strimzi/strimzi-kafka-operator/issues/11685
> > > when found out about this behaviour ;-)
> > >
> > > Thanks,
> > > Paolo
> > >
> > > On Wed, 30 Jul 2025 at 18:55, Jun Rao <ju...@confluent.io.invalid>
> wrote:
> > >
> > > > Hi, Paolo,
> > > >
> > > > There is a PR https://github.com/apache/kafka/pull/20268 for the doc
> > > > change
> > > > for ELR.
> > > >
> > > > Hi, Christo,
> > > >
> > > > Group rebalance is designed so that each partition is only consumed
> by
> > a
> > > > single consumer instance at a time. Share consumer by design allows a
> > > > single partition to be consumed by more than one consumer at any
> time.
> > > So,
> > > > it doesn't need group.coordinator.rebalance.protocols.
> > > >
> > > > Thanks,
> > > >
> > > > Jun
> > > >
> > > > On Wed, Jul 30, 2025 at 6:14 AM Christo Lolov <
> christololov@gmail.com>
> > > > wrote:
> > > >
> > > > > 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.patierno@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Of course, here my +1 (non binding) for the release :-)
> > > > > >
> > > > > > On Wed, 30 Jul 2025 at 08:15, Paolo Patierno <
> > > paolo.patierno@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.maison@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
> > > > > > >> <an...@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 <br...@gmail.com>
> > > > > > >> > Sent: 22 July 2025 16:43
> > > > > > >> > To: dev@kafka.apache.org <de...@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 <
> > > > chia7712@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 <jo...@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.maison@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.maison@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.prat@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>
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > 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>
>

Re: [VOTE] 4.1.0 RC1

Posted by Paolo Patierno <pa...@gmail.com>.

Hi Jun,
yes I think it's clearer now. Thanks.

Paolo

On Thu, 31 Jul 2025 at 22:31, Jun Rao <ju...@confluent.io.invalid> wrote:

> Hi, Paolo,
>
> Thanks for the context. Do you feel that the doc change addresses your
> concern?
>
> Jun
>
> On Thu, Jul 31, 2025 at 5:13 AM Paolo Patierno <pa...@gmail.com>
> wrote:
>
> > Hi Jun,
> > thanks ... that PR came after a long discussion we had in the Strimzi
> > community https://github.com/strimzi/strimzi-kafka-operator/issues/11685
> > when found out about this behaviour ;-)
> >
> > Thanks,
> > Paolo
> >
> > On Wed, 30 Jul 2025 at 18:55, Jun Rao <ju...@confluent.io.invalid> wrote:
> >
> > > Hi, Paolo,
> > >
> > > There is a PR https://github.com/apache/kafka/pull/20268 for the doc
> > > change
> > > for ELR.
> > >
> > > Hi, Christo,
> > >
> > > Group rebalance is designed so that each partition is only consumed by
> a
> > > single consumer instance at a time. Share consumer by design allows a
> > > single partition to be consumed by more than one consumer at any time.
> > So,
> > > it doesn't need group.coordinator.rebalance.protocols.
> > >
> > > Thanks,
> > >
> > > Jun
> > >
> > > On Wed, Jul 30, 2025 at 6:14 AM Christo Lolov <ch...@gmail.com>
> > > wrote:
> > >
> > > > 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.patierno@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Of course, here my +1 (non binding) for the release :-)
> > > > >
> > > > > On Wed, 30 Jul 2025 at 08:15, Paolo Patierno <
> > paolo.patierno@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.maison@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
> > > > > >> <an...@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 <br...@gmail.com>
> > > > > >> > Sent: 22 July 2025 16:43
> > > > > >> > To: dev@kafka.apache.org <de...@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 <
> > > chia7712@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 <jo...@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.maison@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.maison@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.prat@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>
> > > > >
> > > >
> > >
> >
> >
> > --
> > 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>

Re: [VOTE] 4.1.0 RC1

Posted by Jun Rao <ju...@confluent.io.INVALID>.

Hi, Paolo,

Thanks for the context. Do you feel that the doc change addresses your
concern?

Jun

On Thu, Jul 31, 2025 at 5:13 AM Paolo Patierno <pa...@gmail.com>
wrote:

> Hi Jun,
> thanks ... that PR came after a long discussion we had in the Strimzi
> community https://github.com/strimzi/strimzi-kafka-operator/issues/11685
> when found out about this behaviour ;-)
>
> Thanks,
> Paolo
>
> On Wed, 30 Jul 2025 at 18:55, Jun Rao <ju...@confluent.io.invalid> wrote:
>
> > Hi, Paolo,
> >
> > There is a PR https://github.com/apache/kafka/pull/20268 for the doc
> > change
> > for ELR.
> >
> > Hi, Christo,
> >
> > Group rebalance is designed so that each partition is only consumed by a
> > single consumer instance at a time. Share consumer by design allows a
> > single partition to be consumed by more than one consumer at any time.
> So,
> > it doesn't need group.coordinator.rebalance.protocols.
> >
> > Thanks,
> >
> > Jun
> >
> > On Wed, Jul 30, 2025 at 6:14 AM Christo Lolov <ch...@gmail.com>
> > wrote:
> >
> > > 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.patierno@gmail.com
> >
> > > wrote:
> > >
> > > > Of course, here my +1 (non binding) for the release :-)
> > > >
> > > > On Wed, 30 Jul 2025 at 08:15, Paolo Patierno <
> paolo.patierno@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.maison@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
> > > > >> <an...@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 <br...@gmail.com>
> > > > >> > Sent: 22 July 2025 16:43
> > > > >> > To: dev@kafka.apache.org <de...@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 <
> > chia7712@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 <jo...@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.maison@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.maison@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.prat@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>
> > > >
> > >
> >
>
>
> --
> 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>
>

Re: [VOTE] 4.1.0 RC1

Posted by Paolo Patierno <pa...@gmail.com>.

Hi Jun,
thanks ... that PR came after a long discussion we had in the Strimzi
community https://github.com/strimzi/strimzi-kafka-operator/issues/11685
when found out about this behaviour ;-)

Thanks,
Paolo

On Wed, 30 Jul 2025 at 18:55, Jun Rao <ju...@confluent.io.invalid> wrote:

> Hi, Paolo,
>
> There is a PR https://github.com/apache/kafka/pull/20268 for the doc
> change
> for ELR.
>
> Hi, Christo,
>
> Group rebalance is designed so that each partition is only consumed by a
> single consumer instance at a time. Share consumer by design allows a
> single partition to be consumed by more than one consumer at any time. So,
> it doesn't need group.coordinator.rebalance.protocols.
>
> Thanks,
>
> Jun
>
> On Wed, Jul 30, 2025 at 6:14 AM Christo Lolov <ch...@gmail.com>
> wrote:
>
> > 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 <pa...@gmail.com>
> > wrote:
> >
> > > Of course, here my +1 (non binding) for the release :-)
> > >
> > > On Wed, 30 Jul 2025 at 08:15, Paolo Patierno <paolo.patierno@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.maison@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
> > > >> <an...@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 <br...@gmail.com>
> > > >> > Sent: 22 July 2025 16:43
> > > >> > To: dev@kafka.apache.org <de...@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 <
> chia7712@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 <jo...@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.maison@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.maison@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.prat@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>
> > >
> >
>


-- 
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>

Re: [VOTE] 4.1.0 RC1

Posted by Jun Rao <ju...@confluent.io.INVALID>.

Hi, Paolo,

There is a PR https://github.com/apache/kafka/pull/20268 for the doc change
for ELR.

Hi, Christo,

Group rebalance is designed so that each partition is only consumed by a
single consumer instance at a time. Share consumer by design allows a
single partition to be consumed by more than one consumer at any time. So,
it doesn't need group.coordinator.rebalance.protocols.

Thanks,

Jun

On Wed, Jul 30, 2025 at 6:14 AM Christo Lolov <ch...@gmail.com>
wrote:

> 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 <pa...@gmail.com>
> wrote:
>
> > Of course, here my +1 (non binding) for the release :-)
> >
> > On Wed, 30 Jul 2025 at 08:15, Paolo Patierno <pa...@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.maison@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
> > >> <an...@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 <br...@gmail.com>
> > >> > Sent: 22 July 2025 16:43
> > >> > To: dev@kafka.apache.org <de...@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 <chia7712@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 <jo...@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.maison@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.maison@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.prat@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>
> >
>

Re: [VOTE] 4.1.0 RC1

Posted by Christo Lolov <ch...@gmail.com>.

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 <pa...@gmail.com>
wrote:

> Of course, here my +1 (non binding) for the release :-)
>
> On Wed, 30 Jul 2025 at 08:15, Paolo Patierno <pa...@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 <mi...@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
> >> <an...@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 <br...@gmail.com>
> >> > Sent: 22 July 2025 16:43
> >> > To: dev@kafka.apache.org <de...@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 <ch...@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 <jo...@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.maison@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.maison@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.prat@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>
>

Re: [VOTE] 4.1.0 RC1

Posted by Paolo Patierno <pa...@gmail.com>.

Of course, here my +1 (non binding) for the release :-)

On Wed, 30 Jul 2025 at 08:15, Paolo Patierno <pa...@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 <mi...@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
>> <an...@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 <br...@gmail.com>
>> > Sent: 22 July 2025 16:43
>> > To: dev@kafka.apache.org <de...@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 <ch...@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 <jo...@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.maison@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.maison@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.prat@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>

Re: [VOTE] 4.1.0 RC1

Posted by Paolo Patierno <pa...@gmail.com>.

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 <mi...@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
> <an...@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 <br...@gmail.com>
> > Sent: 22 July 2025 16:43
> > To: dev@kafka.apache.org <de...@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 <ch...@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 <jo...@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.maison@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.maison@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.prat@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>

Re: [VOTE] 4.1.0 RC1

Posted by Mickael Maison <mi...@gmail.com>.

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
<an...@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 <br...@gmail.com>
> Sent: 22 July 2025 16:43
> To: dev@kafka.apache.org <de...@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 <ch...@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 <jo...@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.maison@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.maison@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.prat@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
> > >
> >

Re: [VOTE] 4.1.0 RC1

Posted by Andrew Schofield <an...@outlook.com>.

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 <br...@gmail.com>
Sent: 22 July 2025 16:43
To: dev@kafka.apache.org <de...@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 <ch...@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 <jo...@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.maison@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.maison@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.prat@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
> >
>

Re: [VOTE] 4.1.0 RC1

Posted by Kuan-Po Tseng <br...@gmail.com>.

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 <ch...@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 <jo...@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.maison@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.maison@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.prat@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
> >
>

Re: [VOTE] 4.1.0 RC1

Posted by Chia-Ping Tsai <ch...@gmail.com>.

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 <jo...@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 <mi...@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.maison@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.prat@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
>

Re: [VOTE] 4.1.0 RC1

Posted by Chia-Ping Tsai <ch...@gmail.com>.

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 <jo...@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 <mi...@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.maison@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.prat@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
>

Re: [VOTE] 4.1.0 RC1

Posted by Josep Prat <jo...@aiven.io.INVALID>.

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 <mi...@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 <mi...@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.prat@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

Re: [VOTE] 4.1.0 RC1

Posted by Josep Prat <jo...@aiven.io.INVALID>.

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 <mi...@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 <mi...@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.prat@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

Re: [VOTE] 4.1.0 RC1

Posted by Mickael Maison <mi...@gmail.com>.

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 <mi...@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

Re: [VOTE] 4.1.0 RC1

Posted by Mickael Maison <mi...@gmail.com>.

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 <mi...@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