Kafka

Hi Andrew, * verified the gpg signatures * looked at the release notes * checked that the artifacts can be resolved in maven * ran the quickstart and clients against them * ran the docker quickstart * checked the docs Apart from the protocol link pointing to the old docs (I think) all seems good. +1 (binding) Thanks for running the release! Viktor On Wed, Feb 25, 2026 at 2:13 PM Andrew Schofield < schofielaj@apache.org > wrote: > Hello Kafka users, developers and client-developers, > > This is the first candidate for release of Apache Kafka 4.1.2. > > This is the second bug fix release for Apache Kafka 4.1 with fixes as > described in the release notes. > > Release notes for the 4.1.2 release: > https://dist.apache.org/repos/dist/dev/kafka/4.1.2-rc1/RELEASE_NOTES.html > > *** Please download, test and vote by Wednesday, March 4 2026, 9am UTC. > > Kafka's KEYS file containing PGP keys we use to sig...

hi Mark I've added the root cause to the jira ticket. We can continue the discussion there Best, Chia-Ping Marcus Paget < marcuspaget@gmail.com > 於 2026年2月28日週六 上午2:02寫道： > Hello Kafka Users and Developers, > > For KAFKA-19652 - Consumer throughput drops by 10 times with Kafka v3.9.0 > in ZK mode > > I wanted to understand if this is a known issue or an isolated edge case. > It was reported back in August 2025 and subsequently confirmed by 2 other > people, able to reproduce the throughput drop. Although nothing > specifically identifying as a blocker for upgrades to this version or > later. > > Having min.insync.replicas=2 I guess is fairly common, so this would > affect many installations. > > Thanks, > Mark >

Hello Kafka Users and Developers, For KAFKA-19652 - Consumer throughput drops by 10 times with Kafka v3.9.0 in ZK mode I wanted to understand if this is a known issue or an isolated edge case. It was reported back in August 2025 and subsequently confirmed by 2 other people, able to reproduce the throughput drop. Although nothing specifically identifying as a blocker for upgrades to this version or later. Having min.insync.replicas=2 I guess is fairly common, so this would affect many installations. Thanks, Mark

> On Feb 16, 2026, at 1:14 AM, Apoorva Maheshwari via users < users@kafka.apache.org > wrote: > > Hello Team, > > Can you please confirm this pattern, that when we get any vulnerability of jetty and fix from Jetty is available, how soon Kafka release a new version with this Jetty? If you are urgently needing to adopt a Jetty release on your own schedule, rather than Kafka's schedule, you can always adopt new Jetty with your current Kafka version using Maven's <dependencyManagement> feature. This works for most projects, not just Kafka. Of course then you should test that the new combination works acceptably to your requirements, but it at least gives you an independent path forward without needing to pressure Kafka maintainers on new releases with dependency updates, until the normal release process delivers a fixed Kafka artifact. > > Regards, > Apoorva Maheshwari > > From: Apoorva Maheshwari > Sent: 13 Febr...

Hello Kafka users, developers and client-developers, This is the first candidate for release of Apache Kafka 4.1.2. This is the second bug fix release for Apache Kafka 4.1 with fixes as described in the release notes. Release notes for the 4.1.2 release: https://dist.apache.org/repos/dist/dev/kafka/4.1.2-rc1/RELEASE_NOTES.html *** Please download, test and vote by Wednesday, March 4 2026, 9am UTC. Kafka's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/release/kafka/KEYS * Release artifacts to be voted upon (source and binary): https://dist.apache.org/repos/dist/dev/kafka/4.1.2-rc1/ * Docker release artifacts to be voted upon: apache/kafka:4.1.2-rc1 apache/kafka-native:4.1.2-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.2-rc1/javadoc/ * Tag to be voted upon (off 4.1 branch...

Sachin, thanks a lot for your interest. Please read up on how to get started to contribute to ASF projects: https://www.apache.org/foundation/getinvolved.html In particular read about "how to become a committer", which is usually the first step before one gets invited to join the PMC: https://community.apache.org/contributors/ There is also more material about it on the Kafka web page: https://kafka.apache.org/community/developer/#becoming-a-committer More about "roles" in the ASF: https://www.apache.org/foundation/how-it-works/#roles Hope this helps, -Matthias On 2/23/26 5:46 PM, Sachin Bal wrote: > Hello All, > > I too am interested in contributing to the PMC. Can someone please let me > know the eligibility of applying to the same? Thanks in advance > > I look forward to hearing from you > > Kind Regards > Sachin Bal > > > On Mon, 23 Feb, 2026, 05:44 Matthias J. Sax, ...

Hello All, I too am interested in contributing to the PMC. Can someone please let me know the eligibility of applying to the same? Thanks in advance I look forward to hearing from you Kind Regards Sachin Bal On Mon, 23 Feb, 2026, 05:44 Matthias J. Sax, < mjsax@apache.org > wrote: > Dear all, > > The Project Management Committee (PMC) for Apache Kafka is pleased to > announce Andrew Schofield as a new PMC member. > > Andrew has been a Kafka committer since November 2024. He has remained > very active in the community since then, and it's my pleasure to > announce that he has accepted our invitation to become a member of the > Kafka PMC. > > Congratulation Andrew! > > > Matthias, on behalf of the Apache Kafka PMC >