Kafka

Hi Kafka experts, I have a large-scale distributed system that takes around 200K connections to single broker on various topic partitions. I sometimes see my SSL port becomes unresponsive to client with high metadata latency when I sudden spike of around 30K connections (when a broker restarts or it become leader when any other high traffic broker goes for a repair). Is there a reliable way to tune the config to suit the load? Regards, Nanda

Hi Kafka Experts, Even I am looking for comprehensive document on TLS and MTLs with all tyeps of certs. my organisation gives me signed certs in p12 format with a root cert and .key and .cer file. With my limited knowledge of ssl security, when I look at apache kafka ssl document I clueless about where to configure what? Appreciate if someone share documents with little elaboration in above sense for both TLS and mTLS this is how my org signed certs look like. For every Kafka Broker and controller node. hostname.p12 hostname.cer hostname.key myOrgRoot.crt myOrgRoot-Ent.crt Regards, Sunil. On Fri, 6 Mar 2026 at 4:38 AM, Renko Alexander P via users < users@kafka.apache.org > wrote: > Good Day, > Errors trying to start KAFKA 4.1 server with SSL using PEM files. Was > successful starting it without SSL. Under LINUX with Java 17. > > After reading several older posts about PEM files and Kafka nothing is > still working. I'm eith...

Good Day, Errors trying to start KAFKA 4.1 server with SSL using PEM files. Was successful starting it without SSL. Under LINUX with Java 17. After reading several older posts about PEM files and Kafka nothing is still working. I'm either getting 1. Failed to load PEM SSL keystore (when putting keys and certs in files) Or 1. No matching PRIVATE KEY entries in PEM file (putting key and cert contents in the server.properties file) I've tried using encrypted (password) and unencrypted (no password) Private Keys - no difference. My keys/certs/ and CA certs all match up (openssl commands performed to verify) I have a private key, a server certificate (1 cert) and a CA cert (6 certs). There are no clear instructions on whether intermediate or all signing certs should be part of ssl.keystore.certificate.chain= Or, it is unclear how ssl.keystore.location= should be constructed if using files. There are just no good recent examples to be found any...

Hello Kafka users, developers and client-developers, This is the third candidate for release of Apache Kafka 4.0.2. This is a patch release and therefore it contains important bug fixes. Release notes for the 4.0.2 release: https://dist.apache.org/repos/dist/dev/kafka/4.0.2-rc3/RELEASE_NOTES.html *** Please download, test and vote by Wednesday, March 11. 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.0.2-rc3/ * Docker release artifacts to be voted upon: apache/kafka:4.0.2-rc3 apache/kafka-native:4.0.2-rc3 https://dist.apache.org/repos/dist/dev/kafka/4.0.2-rc3/kafka_2.13-4.0.2.tgz * 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.0.2-rc3/javadoc/ * Tag to be voted upon (off 4...

Hi Andrew, Thanks for running the release. * Built from source with openjdk 17 and 21 * Verified basic produce/consume * Validated the checksums and keys * Ran basic quickstart using apache/kafka:4.1.2-rc1 and apache/kafka-native:4.1.2-rc1 docker image The protocol link is changed to https://kafka.apache.org/41/design/protocol/ . I created a PR to fix it. https://github.com/apache/kafka/pull/21628 Thank you, PoAn > On Mar 2, 2026, at 6:39 PM, Viktor Somogyi-Vass < viktorsomogyi@gmail.com > wrote: > > 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 >...

Unsubscribe On Wed, Mar 4, 2026 at 5:02 AM Josep Prat via users < users@kafka.apache.org > wrote: > Hi, > I think our release process doesn't currently specify when to update this > page. Many release managers update it after the release is done. Let me add > the ones that we have in flight in that page. > > Best, > > On Wed, Mar 4, 2026 at 10:52 AM Xiong, Benson < benson.xiong01@sap.com > > wrote: > > > Hi Prat, > > > > Thank you for the information. Where can we watch the status of this > > release? I originally thought it was tracked in > > https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan . > > > > > > Regards, > > Benson > > > > *From: *Josep Prat < josep.prat@aiven.io > > > *Date: *Wednesday, March 4, 2026 at 17:30 > > *To: * users@kafka.apache.org < users@kafka.apache.org > > > *Cc: *Xiong...

Hi, I think our release process doesn't currently specify when to update this page. Many release managers update it after the release is done. Let me add the ones that we have in flight in that page. Best, On Wed, Mar 4, 2026 at 10:52 AM Xiong, Benson < benson.xiong01@sap.com > wrote: > Hi Prat, > > Thank you for the information. Where can we watch the status of this > release? I originally thought it was tracked in > https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan . > > > Regards, > Benson > > *From: *Josep Prat < josep.prat@aiven.io > > *Date: *Wednesday, March 4, 2026 at 17:30 > *To: * users@kafka.apache.org < users@kafka.apache.org > > *Cc: *Xiong, Benson < benson.xiong01@sap.com > > *Subject: *Re: Kafka 4.1.2 release plan > > You don't often get email from josep.prat@aiven.io . Learn why this is > important < https://aka.ms/LearnAboutSenderI...