Kafka

In a personal cluster I used to have three kraft controllers, using Kafka 4.2.0. Because of "reasons" (the cluster is a lab), I downsized the cluster and now I only use a controller, just modifying "controller.quorum.voters" to include only the surviving controller. Working fine so far. Yes, I know that a single controller is a risk. Today I upgraded the brokers and the controller to Kafka 4.3.0 and I tried to upgrade de cluster version using "kafka-features.sh upgrade --release-version 4.3", but it is complaining that "old" controllers, offline and destroyed, are not compatible (they were Kafka 4.2.0 at the time of decommission). 1. How can I get rid of those dead controllers still haunting me? 2. I have tried to migrate to dynamic controller membership, but just changing "controller.quorum.voters" to "controller.quorum.bootstrap.server" doesn't work, although it is documented in <h...

This vote passes with 5 +1 votes (3 bindings) and no 0 or -1 votes. +1 votes PMC Members: * Mickael Maison * Lucas Brutschy * Chia-Ping Tsai Committers: * No votes Community: * Jakub Scholz * Maroš Orsák 0 votes * No votes -1 votes * No votes Vote thread: https://lists.apache.org/thread/o3rcbdwv2sl264x71yy26tv71s1mxmkv, https://lists.apache.org/thread/y5m2p9572sv7x2odc8b4yqzk7yr1z786 I'll continue with the release process and the release announcement will follow in the next few days. PoAn

Hi all, We're upgrading a Kafka Streams service from 3.9.0 to 4.x and ran into a behavioral change in REPLACE_THREAD recovery that we'd like to understand whether it's intended. Summary When the StreamsUncaughtExceptionHandler returns REPLACE_THREAD, recovery time jumps from sub-second (3.9.x) to ~`session.timeout.ms(45 s default) starting with4.0. We've traced this to the dying consumer no longer sending a LeaveGroup` request on shutdown — the broker therefore has to wait for the session to expire before it triggers a rebalance. This appears to be the combined effect of KIP-1092 (which added the GroupMembershipOperation filter in AbstractCoordinator) and Streams' replaceStreamThread() passing REMAIN_IN_GROUP to the consumer's close path. We understand the rationale (avoid partition bouncing for stateful apps where the new thread starts in the same JVM), but the 45 s floor undermines KIP-671's promise of "fast in-place recovery from ...

Hi all, We're upgrading a Kafka Streams service from 3.9.0 to 4.x and ran into a behavioral change in REPLACE_THREAD recovery that we'd like to understand whether it's intended. Summary When the StreamsUncaughtExceptionHandler returns REPLACE_THREAD, recovery time jumps from sub-second (3.9.x) to ~`session.timeout.ms(45 s default) starting with4.0. We've traced this to the dying consumer no longer sending a LeaveGroup` request on shutdown — the broker therefore has to wait for the session to expire before it triggers a rebalance. This appears to be the combined effect of KIP-1092 (which added the GroupMembershipOperation filter in AbstractCoordinator) and Streams' replaceStreamThread() passing REMAIN_IN_GROUP to the consumer's close path. We understand the rationale (avoid partition bouncing for stateful apps where the new thread starts in the same JVM), but the 45 s floor undermines KIP-671's promise of "fast in-place recovery from ...

Hi, Besides manual checks, I have also run the Strimzi test container tests on Aarch64 image build from https://dist.apache.org/repos/dist/dev/kafka/4.2.1-rc5/kafka_2.13-4.2.1.tgz, all tests passed without issues. +1 (non-binding), Cheers, Maros št 28. 5. 2026 o 6:05 Chia-Ping Tsai <chia7712@apache.org> napísal(a): > +1 (binding) > > - Run E2E tests locally; all passed with a few retries. > - Set up a 3-node cluster and ran a simple producer/consumer workflow; no > obvious performance regression. > - Run unit/integration tests locally; all passed with minimal retries. > > Best, > Chia-Ping > > On 2026/05/14 10:41:11 PoAn Yang wrote: > > Hello Kafka users, developers and client-developers, > > > > This is the third candidate for release of Apache Kafka 4.2.1. > > > > This is the first bug fix release for Apache Kafka 4.2 with fixes as > > described in the release notes. In the t...

+1 (binding) - Run E2E tests locally; all passed with a few retries. - Set up a 3-node cluster and ran a simple producer/consumer workflow; no obvious performance regression. - Run unit/integration tests locally; all passed with minimal retries. Best, Chia-Ping On 2026/05/14 10:41:11 PoAn Yang wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate for release of Apache Kafka 4.2.1. > > This is the first bug fix release for Apache Kafka 4.2 with fixes as > described in the release notes. In the third candidate, it adds KAFKA-20572. > > Release notes for the 4.2.1 release: > https://dist.apache.org/repos/dist/dev/kafka/4.2.1-rc5/RELEASE_NOTES.html > > Please download, test and vote by Thursday, May 20, 9pm PT. > > 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 bi...

Thanks to Mickael for driving the 4.3.0 release > Mickael Maison <mimaison@apache.org> 於 2026年5月22日 晚上8:29 寫道： > > The Apache Kafka community is pleased to announce the release for > Apache Kafka 4.3.0 > > All of the changes in this release can be found in the release notes: > https://www.apache.org/dist/kafka/4.3.0/RELEASE_NOTES.html > > > An overview of the release can be found in our announcement blog post: > https://kafka.apache.org/blog/2026/05/22/apache-kafka-4.3.0-release-announcement/ > > You can download the source and binary release (Scala 2.13) from: > https://kafka.apache.org/downloads#4.3.0 > > --------------------------------------------------------------------------------------------------- > > > Apache Kafka is a distributed streaming platform with four core APIs: > > > ** The Producer API allows an application to publish a stream of records to > one or more ...

The Apache Kafka community is pleased to announce the release for Apache Kafka 4.3.0 All of the changes in this release can be found in the release notes: https://www.apache.org/dist/kafka/4.3.0/RELEASE_NOTES.html An overview of the release can be found in our announcement blog post: https://kafka.apache.org/blog/2026/05/22/apache-kafka-4.3.0-release-announcement/ You can download the source and binary release (Scala 2.13) from: https://kafka.apache.org/downloads#4.3.0 --------------------------------------------------------------------------------------------------- Apache Kafka is a distributed streaming platform with four core APIs: ** The Producer API allows an application to publish a stream of records to one or more Kafka topics. ** The Consumer API allows an application to subscribe to one or more topics and process the stream of records produced to them. ** The Streams API allows an application to act as a stream processor, consuming an inpu...

+1 (non-binding). I used the staged binaries and Maven artifacts ... and did some manual testing and tested it with Strimzi tests as well. All seems to work fine. Jakub On Thu, May 14, 2026 at 12:42 PM PoAn Yang <yangpoan@gmail.com> wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate for release of Apache Kafka 4.2.1. > > This is the first bug fix release for Apache Kafka 4.2 with fixes as > described in the release notes. In the third candidate, it adds > KAFKA-20572. > > Release notes for the 4.2.1 release: > https://dist.apache.org/repos/dist/dev/kafka/4.2.1-rc5/RELEASE_NOTES.html > > Please download, test and vote by Thursday, May 20, 9pm PT. > > 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/...

Hi, I'm now closing this vote, it has passed. I'll send the results and I'll continue with the release process. Thanks, Mickael On Tue, May 19, 2026 at 5:50 PM Federico Valeri <fedevaleri@gmail.com> wrote: > > Hi Mickael, > > I ran various test client applications on Java 21 using the staged > Maven artifacts. > > +1 non binding > > Thanks > > On Tue, May 19, 2026 at 2:02 PM Keith W <keith.wall@gmail.com> wrote: > > > > I tested out the staged Maven artifacts from > > https://repository.apache.org/content/groups/staging/org/apache/kafka/ > > against the Kroxylicious test suite. > > This relies on both kafka client and server artefacts. No issues encountered. > > > > Thank you > > > > +1 (non binding) > > > > On Fri, 15 May 2026 at 15:58, Josep Prat via dev <dev@kafka.apache.org> wrote: > > > > > > Hi Micka...

Hi Luke, Need answers to the following questions – 1. When is the next release planned which have fix for this CVE. 2. What log4j/jetty/Jackson-core version will be used in this upcoming kafka release. Share the JIRA links if available. Regards Vivek From: Luke Chen <showuon@gmail.com> Sent: 15 May 2026 12:39 To: users@kafka.apache.org Cc: users-subscribe@kafka.apache.org; Vivek Agarwal B <vivek.b.agarwal@ericsson.com>; Apoorva Maheshwari <apoorva.maheshwari@ericsson.com> Subject: Re: Kafka new version info You don't often get email from showuon@gmail.com<mailto:showuon@gmail.com>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi Apoorva, This is an open source project, so you can search in the JIRA or check the source code to find the answer. Like the first CVE-2025-67030, you will find this ticket after searching it: https://issues.apache.org/jira/browse/KAFKA-20373 And it showed it...

Hi Mickael, I ran various test client applications on Java 21 using the staged Maven artifacts. +1 non binding Thanks On Tue, May 19, 2026 at 2:02 PM Keith W <keith.wall@gmail.com> wrote: > > I tested out the staged Maven artifacts from > https://repository.apache.org/content/groups/staging/org/apache/kafka/ > against the Kroxylicious test suite. > This relies on both kafka client and server artefacts. No issues encountered. > > Thank you > > +1 (non binding) > > On Fri, 15 May 2026 at 15:58, Josep Prat via dev <dev@kafka.apache.org> wrote: > > > > Hi Mickael, > > > > I did the following: > > - checked the signatures and checksums > > - build from source > > - ran the test locally > > - Tested Docker Images: > > -- can start > > -- can create topics > > - ran quickstart > > - ran sample apps with consumer groups > > - checked J...

I tested out the staged Maven artifacts from https://repository.apache.org/content/groups/staging/org/apache/kafka/ against the Kroxylicious test suite. This relies on both kafka client and server artefacts. No issues encountered. Thank you +1 (non binding) On Fri, 15 May 2026 at 15:58, Josep Prat via dev <dev@kafka.apache.org> wrote: > > Hi Mickael, > > I did the following: > - checked the signatures and checksums > - build from source > - ran the test locally > - Tested Docker Images: > -- can start > -- can create topics > - ran quickstart > - ran sample apps with consumer groups > - checked Java client interaction from artifacts (admin, producer, consumer > and streams) > - checked Tiered Storage offloads to remote storage (with Aiven's plugin) > - checked Kafka Connect > > +1 (binding for me) > > Thanks for running the release! > > Best, > > On Fri, May 15, 2026 a...

Hi Mickael, I did the following: - checked the signatures and checksums - build from source - ran the test locally - Tested Docker Images: -- can start -- can create topics - ran quickstart - ran sample apps with consumer groups - checked Java client interaction from artifacts (admin, producer, consumer and streams) - checked Tiered Storage offloads to remote storage (with Aiven's plugin) - checked Kafka Connect +1 (binding for me) Thanks for running the release! Best, On Fri, May 15, 2026 at 3:52 PM Lianet Magrans <lianetm@apache.org> wrote: > Hi Mickael, > > I did the following on RC2: > - verified the checksums and signature > - downloaded and build from source (java 21) + run quickstart > - played with basic produce/consume, classic and consumer groups, mixed > groups, online upgrade/downgrade > - downloaded docker images & run quick start with both > - browsed the docs > > +1 (binding) > ...

Hi Mickael, I did the following on RC2: - verified the checksums and signature - downloaded and build from source (java 21) + run quickstart - played with basic produce/consume, classic and consumer groups, mixed groups, online upgrade/downgrade - downloaded docker images & run quick start with both - browsed the docs +1 (binding) Thanks for running the release! Lianet On Fri, May 15, 2026 at 9:17 AM Jakub Scholz <jakub@scholz.cz> wrote: > I did the same tests as with the previous RCs, all using the staged > binaries and everything seems to work fine. +1 (non-binding) from me. > > Thanks for running the release Mickael. > > Jakub > > On Wed, May 13, 2026 at 2:15 PM Mickael Maison <mickael.maison@gmail.com> > wrote: > > > Hello Kafka users, developers and client-developers, > > > > This is the 3rd candidate for release of Apache Kafka 4.3.0. > > > > Since RC2, we've added...

I did the same tests as with the previous RCs, all using the staged binaries and everything seems to work fine. +1 (non-binding) from me. Thanks for running the release Mickael. Jakub On Wed, May 13, 2026 at 2:15 PM Mickael Maison <mickael.maison@gmail.com> wrote: > Hello Kafka users, developers and client-developers, > > This is the 3rd candidate for release of Apache Kafka 4.3.0. > > Since RC2, we've added fixes for: > - https://issues.apache.org/jira/browse/KAFKA-20380 > - https://issues.apache.org/jira/browse/KAFKA-20571 > - https://issues.apache.org/jira/browse/KAFKA-20572 > > Release notes for the 4.3.0 release: > https://dist.apache.org/repos/dist/dev/kafka/4.3.0-rc2/RELEASE_NOTES.html > > *** Please download, test and vote by May 20, 5pm CEST > > Kafka's KEYS file containing PGP keys we use to sign the release: > https://downloads.apache.org/kafka/KEYS > > * Release artifacts to b...

Dear Apache Kafka Community, I am an independent developer building *Debo Data Studio*, a unified visual ETL platform recently discussed on the Apache Incubator mailing list (thread: https://lists.apache.org/thread/ctw3g5v4mf8o5dko1w1xvmwgsq97f6kt). Following the community-building advice I received from the Incubator members, I am reaching out to the Kafka community to discuss a specific architectural direction I am exploring regarding event-driven data pipelines. *The Proposal: PostgreSQL LISTEN/NOTIFY for Kafka-like Functionality* While Apache Kafka is the industry standard for high-throughput event streaming, I have observed that for many ETL and small-to-medium scale synchronization tasks, the operational overhead of managing a Kafka cluster can be a significant barrier. I am implementing a feature in Debo Data Studio that uses *PostgreSQL SQL scripts and LISTEN/NOTIFY functionality* to mimic core Kafka-like behaviors for smaller environments: - ...

Hi Apoorva, This is an open source project, so you can search in the JIRA or check the source code to find the answer. Like the first CVE-2025-67030, you will find this ticket after searching it: https://issues.apache.org/jira/browse/KAFKA-20373 And it showed it'll be included in v4.2.1/v4.3.0. If you find it is not fixed yet, submitting PRs to fix them is highly appreciated. Thank you, Luke On Fri, May 15, 2026 at 2:18 PM Apoorva Maheshwari via users < users@kafka.apache.org> wrote: > Hello Team, > > > > Could you please confirm the plan to release a new Kafka version that > includes fixes for vulnerabilities identified primarily in transient > dependencies such as Jetty, log4j, Jackson, and a few others? > > > > Below is the list of identified vulnerabilities for reference: > > > > CVE-2025-67030 > > CVE-2026-39882 > > CVE-2026-41078 > > CVE-2026-40894 > > ...

Congratulations Sean! On Sat, May 2, 2026, at 2:31 AM, Igor Soarez wrote: > Congratulations Sean! > > -- > Igor > > On Wed, Apr 29, 2026, at 19:48, Chia-Ping Tsai wrote: > > The Project Management Committee (PMC) for Apache Kafka is pleased to > > announce Sean Quah as a new Kafka committer. > > > > Sean is a true Kafka expert who has made numerous significant contributions > > to the project. If you are amazed by the new consumer protocol, we owe a > > huge thanks to Sean for helping build this foundational feature. Honestly, > > I am so proud to be the one sharing this exciting news with you all. > > > > Please join me in welcoming and congratulating Sean! > > > > Chia-Ping Tsai > > On behalf of the Apache Kafka PMC > > >

Hello Kafka users, developers and client-developers, This is the third candidate for release of Apache Kafka 4.2.1. This is the first bug fix release for Apache Kafka 4.2 with fixes as described in the release notes. In the third candidate, it adds KAFKA-20572. Release notes for the 4.2.1 release: https://dist.apache.org/repos/dist/dev/kafka/4.2.1-rc5/RELEASE_NOTES.html Please download, test and vote by Thursday, May 20, 9pm PT. 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.2.1-rc5/ * Docker release artifacts to be voted upon: apache/kafka:4.2.1-rc5 apache/kafka-native:4.2.1-rc5 * 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.2.1-rc5/javadoc/index.html * Tag to be voted upon (o...

HI KAFKA Users, We have two configured Linux Kafka on the 2 environment UAT and PRODUCTION. Environment through same warning simultaneous Every 12 hours once same exact time. So can anyone please share the Root cause of the issue and solution of the issue. Issue has been observed last month 17 APR 2026 onwards. Thanks and Regards, THIRUVARASAMOORTHI R. From: R THIRUVARASAMOORTHI Sent: 06 May 2026 10:34 To: 'users@kafka.apache.org' <users@kafka.apache.org> Cc: RAJARAM KUMAR <RAJARAM.KUMAR2@mahindra.com> Subject: KAFKA 2.13-3.3.1 Zookeeper issue Hello Kafka Community, We are currently using Kafka version kafka_2.13-3.3.1 on a Linux Ubuntu server. This setup has been running successfully for the past two years to integrate two PLM [3DExperience and Teamcenter] applications. In recent days, we have encountered recurring issues in the Zookeeper services, and it leads to bring down the zookeeper service within 10 days: Every 12 hours/24 hours, Zook...

I had an idea for a Kafka Streams implementation of Allen’s Temporal Logic (from the early 80’s), and came up with this. It’s just a toy/demo but I thought it was pretty cool what the AI (with significant help from me) could come up with in a few hours of effort. Article is here: https://www.linkedin.com/pulse/kafka-streams-implementation-allens-temporal-logic-llms-paul-brebner-j247e/ Code is here: https://github.com/paul-brebner/kafka-streams-allen-intervals/tree/main Enjoy! -- Regards, Paul Brebner NetApp Instaclustr Technology Evangelist Read my blogs at https://www.instaclustr.com/paul-brebner/ Follow me on https://www.linkedin.com/in/paul-brebner-0a547b4/

Hello Kafka users, developers and client-developers, This is the 3rd candidate for release of Apache Kafka 4.3.0. Since RC2, we've added fixes for: - https://issues.apache.org/jira/browse/KAFKA-20380 - https://issues.apache.org/jira/browse/KAFKA-20571 - https://issues.apache.org/jira/browse/KAFKA-20572 Release notes for the 4.3.0 release: https://dist.apache.org/repos/dist/dev/kafka/4.3.0-rc2/RELEASE_NOTES.html *** Please download, test and vote by May 20, 5pm CEST Kafka's KEYS file containing PGP keys we use to sign the release: https://downloads.apache.org/kafka/KEYS * Release artifacts to be voted upon (source and binary): https://dist.apache.org/repos/dist/dev/kafka/4.3.0-rc2/ * Docker release artifacts to be voted upon: apache/kafka:4.3.0-rc2 apache/kafka-native:4.3.0-rc2 * 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.3....

Hi, I did the following: - checked the signatures and checksums - built from source - ran the tests - Tested Docker Images: -- can start -- can create topics - ran quickstart - ran sample apps with consumer groups - checked Java client interaction from artifacts (admin, producer, consumer and streams) - checked Tiered Storage offloads to remote storage (with Aiven's plugin) - checked Kafka Connect Verified on Linux with JDK 21 +1 (binding) On Tue, May 12, 2026 at 5:31 PM Lucas Brutschy via dev <dev@kafka.apache.org> wrote: > +1 (non-binding) > > Verified on macOS arm64, JDK 17: > > * GPG signatures and SHA512 checksums for source, binary, and > site-docs tarballs > * LICENSE/NOTICE present > * Built source with ./gradlew jar — BUILD SUCCESSFUL > * git tag 4.2.1-rc4 commit matches the shipped jar's > kafka-version.properties commitId > * KRaft quickstart: format --standalone, broker start, > t...

+1 (non-binding) Verified on macOS arm64, JDK 17: * GPG signatures and SHA512 checksums for source, binary, and site-docs tarballs * LICENSE/NOTICE present * Built source with ./gradlew jar — BUILD SUCCESSFUL * git tag 4.2.1-rc4 commit matches the shipped jar's kafka-version.properties commitId * KRaft quickstart: format --standalone, broker start, topic/produce/consume * KIP-1071 streams group: ran WordCountDemo with group.protocol=streams; logs show StreamsGroupHeartbeatRequestManager and counts aggregate correctly across rounds. Exercised kafka-streams-groups.sh --list/--describe/--members/--state/--offsets/ --verbose; --reset-offsets correctly rejected while Stable, accepted once Empty * Docker images apache/kafka and apache/kafka-native: both start, produce/consume works against each, commitId matches the tag * Documentation, javadoc, protocol, release-notes, and GitHub tag URLs all reachable * Maven staging artifacts present with La...

Hi Mickael, I did the following: - verified the checksums and signatures - build from source (java 21) -> run quickstart, basic produce/consume with Classic and Consumer groups - run basic consume/produce on both docker images - run the network degrade sys test that was failing on your side. I got a green run for the test_rate on 4.3 after some retries https://confluent-open-source-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/trunk/2026-05-11--001.f3134388-b3df-48e5-ae8b-98d07ddfff55--1778526564--apache--4.3--84b51283d6/report.html +1 (binding) Best! Lianet On Mon, May 11, 2026 at 2:51 PM Jakub Scholz <jakub@scholz.cz> wrote: > @Maciej: You mean within Strimzi? The system tests we have covering OAuth > passed. But I have not done any special testing for that as OAuth is not > really my specialty. > > Jakub > > On Mon, May 11, 2026 at 5:36 PM Maciej Malecki <emaciejm@gmail.com> wrote: > > ...

@Maciej: You mean within Strimzi? The system tests we have covering OAuth passed. But I have not done any special testing for that as OAuth is not really my specialty. Jakub On Mon, May 11, 2026 at 5:36 PM Maciej Malecki <emaciejm@gmail.com> wrote: > Does this version work with strimzi oauth 0.17.1? > > *__________________* > *Regards,* > > *Maciej Małecki* > > pon., 11 maj 2026, 16:58 użytkownik Jakub Scholz <jakub@scholz.cz> > napisał: > > > I used the staged binaries and Maven artifacts, and: > > * did some manual smoke testing > > * Run it within Strimzi and its system tests > > > > All seems to work fine, so +1 (non-binding). > > > > Thanks & Regards > > Jakub > > > > On Tue, May 5, 2026 at 1:41 PM Mickael Maison <mickael.maison@gmail.com> > > wrote: > > > > > Hello Kafka users, developers and client-developers, >...

Does this version work with strimzi oauth 0.17.1? *__________________* *Regards,* *Maciej Małecki* pon., 11 maj 2026, 16:58 użytkownik Jakub Scholz <jakub@scholz.cz> napisał: > I used the staged binaries and Maven artifacts, and: > * did some manual smoke testing > * Run it within Strimzi and its system tests > > All seems to work fine, so +1 (non-binding). > > Thanks & Regards > Jakub > > On Tue, May 5, 2026 at 1:41 PM Mickael Maison <mickael.maison@gmail.com> > wrote: > > > Hello Kafka users, developers and client-developers, > > > > This is the 2nd candidate for release of Apache Kafka 4.3.0. > > > > This release includes 25 KIPs bringing improvements to all components. > > > > Release notes for the 4.3.0 release: > > > https://dist.apache.org/repos/dist/dev/kafka/4.3.0-rc1/RELEASE_NOTES.html > > > > *** Please download, test and vote ...

I used the staged binaries and Maven artifacts, and: * did some manual smoke testing * Run it within Strimzi and its system tests All seems to work fine, so +1 (non-binding). Thanks & Regards Jakub On Tue, May 5, 2026 at 1:41 PM Mickael Maison <mickael.maison@gmail.com> wrote: > Hello Kafka users, developers and client-developers, > > This is the 2nd candidate for release of Apache Kafka 4.3.0. > > This release includes 25 KIPs bringing improvements to all components. > > Release notes for the 4.3.0 release: > https://dist.apache.org/repos/dist/dev/kafka/4.3.0-rc1/RELEASE_NOTES.html > > *** Please download, test and vote by May 11, 5pm CEST > > Kafka's KEYS file containing PGP keys we use to sign the release: > https://downloads.apache.org/kafka/KEYS > > * Release artifacts to be voted upon (source and binary): > https://dist.apache.org/repos/dist/dev/kafka/4.3.0-rc1/ > > * Docker relea...

Thanks, I got the permissions and I published the KIP and started the discussion. Appreciate you checking about this. Thanks, Sruthi On Mon, May 11, 2026 at 2:16 AM Josep Prat via users <users@kafka.apache.org> wrote: > Hi Sruthi, > Luke already granted you access a few hours ago. Is it still an issue? > > Best, > > On Mon, May 11, 2026 at 10:21 AM Sruthi Sathyamoorthy < > sruthi9610@gmail.com> > wrote: > > > Hello Apache Kafka Community, > > > > I am Sruthi. I am new to the Apache Kafka community. I created my JIRA > > account with my email id and I am also trying to create a KIP for which > I > > created an Apache wiki (Confluence) account. I am unable to assign tasks > to > > me in the JIRA page or find an option to create a confluent page under > KIP > > indexes. Do I need any permissions? The first draft of KIP for this JIRA > > https://issues.apache.org/j...

Hi Sruthi, Luke already granted you access a few hours ago. Is it still an issue? Best, On Mon, May 11, 2026 at 10:21 AM Sruthi Sathyamoorthy <sruthi9610@gmail.com> wrote: > Hello Apache Kafka Community, > > I am Sruthi. I am new to the Apache Kafka community. I created my JIRA > account with my email id and I am also trying to create a KIP for which I > created an Apache wiki (Confluence) account. I am unable to assign tasks to > me in the JIRA page or find an option to create a confluent page under KIP > indexes. Do I need any permissions? The first draft of KIP for this JIRA > https://issues.apache.org/jira/browse/KAFKA-20320 is ready and would like > to upload it. > > My wiki confluent user name is *ssathy10*. My JIRA name is also *ssathy10.* > > Thanks, > Sruthi > -- [image: Aiven] <https://www.aiven.io> *Josep Prat* Sr Engineering Director, Streaming Services, *Aiven* josep.prat@aiven.io ...