Kafka

Thanks to Bill Bejeck for running the release! Bill Bejeck <bbejeck@apache.org> 於 2026年6月26日週五 上午1:08寫道： > The Apache Kafka community is pleased to announce the release for > Apache Kafka 4.3.1 > > This bug-fix release includes several critical fixes as documented in the > release notes. > > All of the changes in this release can be found in the release notes: > https://www.apache.org/dist/kafka/4.3.1/RELEASE_NOTES.html > > You can download the source and binary release from: > https://kafka.apache.org/downloads#4.3.1 > > > --------------------------------------------------------------------------------------------------- > > > 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 > t...

The Apache Kafka community is pleased to announce the release for Apache Kafka 4.3.1 This bug-fix release includes several critical fixes as documented in the release notes. All of the changes in this release can be found in the release notes: https://www.apache.org/dist/kafka/4.3.1/RELEASE_NOTES.html You can download the source and binary release from: https://kafka.apache.org/downloads#4.3.1 --------------------------------------------------------------------------------------------------- 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 input stream from one or more topics and producing an output stream to one or more...

You need to request an account: https://selfserve.apache.org/jira-account.html On 6/24/26 6:02 PM, sunil chaudhari wrote: > H, > How to create Jira ticket for crucial custom parittioning requirement? >

hi Are you looking for an official way to add "labels" to topics? If so, there is no such mechanism for now. One workaround is to create a compacted topic to store them. Another is to encode the labels within the topic name, such as a-b-c-d. If topic-level labels are a crucial feature for you, please feel free to open a JIRA and KIP for it. Best, Chia-Ping On 2026/04/13 03:07:15 Satyaprakash Dwibedi via users wrote: > Hello Kafka Community, > > We have a use case that requires attaching custom metadata to topics — > things like SLA, durability guarantees, and PagerDuty account references. > While exploring this in Kafka 4.2.0, we noticed an interesting > inconsistency between broker-level and topic-level configuration behavior. > > Broker-level custom configs work fine: > > Running the following command succeeds without errors: > > ./bin/kafka-configs.sh --bootstrap-server localhost:9092 \ > --entity-typ...

hi Jesús Have you tried to use `kafka-metadata-quorum.sh` to remove those "offline" nodes from voters? For example: ``` bin/kafka-metadata-quorum.sh --command remove-controller --controller-id ``` Best, Chia-Ping On 2026/05/29 06:32:27 Jesus Cea wrote: > 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 wer...

This vote passes with 4 +1 votes (3 bindings) and no 0 or -1 votes. +1 votes PMC Members: * Matthias Sax * Lianet Magrans * Christo Lolov Community: * Rich Bowen 0 votes * No votes -1 votes * No votes Vote thread: https://lists.apache.org/thread/dkoq1ykhmzqobsqvk4tgotso6cp7o53q I'll continue with the release process and the release announcement will follow in the next few days. Bill Bejeck

We have observed a similar behavior: Currently, we're upgrading our Spring Boot application from 4.0.6 to 4.1.0 which in turn upgrades Kafka from 4.1.2 to 4.2.1. We have observed that the behavior of REPLACE_THREAD / StreamsUncaughtExceptionHandler has changed. In Kafka 4.1.2, when REPLACE_THREAD was returned, the old StreamThread shut down and left the group, and the new thread could then resume work immediately. In Kafka 4.2.1, when REPLACE_THREAD is returned, the old StreamThread remains in the group for max.poll.interval.ms milliseconds and that is how long it takes for the new StreamThread to start getting work. We believe that this is caused by https://github.com/apache/kafka/commit/68f1da84740092dbd5ebb49ae62035174758b98b#diff-ab27af136b0c45ed402ec44368a91380b018bf06f1a9722324fe6be8d5220f7dR491-R978 where leaveGroupRequested is now set to false / REMAIN_IN_GROUP, which previously was set to true / LEAVE_GROUP. We are using the classic protocol. On 2026/05/2...