Kafka

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

Hello Kafka users, developers and client-developers, This is the second release candidate of Apache Kafka 4.3.1. This is a bugfix release for the 4.3 line. The most significant fix is KAFKA-20616, a critical native memory leak in Kafka Streams caused by RocksDB ColumnFamily handles and ColumnFamilyOptions not being released (notably the offsets column family added for KIP-1035). The release also includes: - KAFKA-20663: Kafka Streams stale-offset / OffsetOutOfRangeException on restart (StateDirectory task-lock release on startup-manager close, and returning the committed offset from the newest segment first) - KAFKA-20673: AdminClient partition-leader APIs hang when a cached leader has left the cluster - KAFKA-20634 / KAFKA-20635: spurious group-coordinator errors after a partition leadership change - KAFKA-20535: improved async consumer CPU usage under low max.poll.records - Additional documentation updates (KIP-1035, KIP-1271 headers-aware state ...

Hello Kafka users, developers and client-developers, This is the first candidate for release of Apache Kafka 4.3.1. This is a bugfix release for the 4.3 line. The most significant fix is KAFKA-20616, a critical native memory leak in Kafka Streams caused by RocksDB ColumnFamily handles and ColumnFamilyOptions not being released (notably the offsets column family added for KIP-1035). The release also includes: - KAFKA-20663: Kafka Streams stale-offset / OffsetOutOfRangeException on restart (StateDirectory task-lock release on startup-manager close, and returning the committed offset from the newest segment first) - KAFKA-20673: AdminClient partition-leader APIs hang when a cached leader has left the cluster - KAFKA-20634 / KAFKA-20635: spurious group-coordinator errors after a partition leadership change - KAFKA-20535: improved async consumer CPU usage under low max.poll.records - Additional documentation updates (KIP-1035, KIP-1271 headers-aware sta...

Thanks for running the release, PoAn! On 2026/06/03 01:28:38 Eric Chang wrote: > Thanks for managing the release PoAn! > > On 2026/06/02 14:11:05 PoAn Yang wrote: > > The Apache Kafka community is pleased to announce the release for Apache > > Kafka 4.2.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.2.1/RELEASE_NOTES.html > > > > An overview of the release can be found in our announcement blog post: > > https://kafka.apache.org/blog > > > > You can download the source and binary release from: > > https://kafka.apache.org/downloads#4.2.1 > > > > --------------------------------------------------------------------------------------------------- > > > > > > Apache ...

Thanks for managing the release PoAn! On Wed, Jun 3, 2026 at 7:53 PM jian fu <fujian1115@gmail.com> wrote: > Thanks for PoAn to manage this release > > Regards > Jian > > Christo Lolov <christololov@gmail.com>于2026年6月3日 周三19:28写道： > > > Thank you for running the release, PoAn! > > > > On Tue, 2 Jun 2026 at 19:50, Lucas Brutschy via dev > > <dev@kafka.apache.org> wrote: > > > > > > Thanks for managing the release PoAn! > > > > > > On Tue, Jun 2, 2026 at 5:46 PM Chia-Ping Tsai <chia7712@gmail.com> > > wrote: > > > > > > > > > > > > Thanks for PoAn to manage this release > > > > > > > > > sunil chaudhari <sunilmchaudhari05@gmail.com> 於 2026年6月2日 晚上11:23 > > 寫道： > > > > > > > > > > Hi, > > > > > Thanks for announcement. > > ...

Thanks for PoAn to manage this release Regards Jian Christo Lolov <christololov@gmail.com>于2026年6月3日 周三19:28写道： > Thank you for running the release, PoAn! > > On Tue, 2 Jun 2026 at 19:50, Lucas Brutschy via dev > <dev@kafka.apache.org> wrote: > > > > Thanks for managing the release PoAn! > > > > On Tue, Jun 2, 2026 at 5:46 PM Chia-Ping Tsai <chia7712@gmail.com> > wrote: > > > > > > > > > Thanks for PoAn to manage this release > > > > > > > sunil chaudhari <sunilmchaudhari05@gmail.com> 於 2026年6月2日 晚上11:23 > 寫道： > > > > > > > > Hi, > > > > Thanks for announcement. > > > > Are these changes available in 4.3.0 > > > > We are setting up new cluster version 4.3.0. > > > > Dont want to miss these bug fixes. > > > > > > > > Regards, > > > > S...

Thank you for running the release, PoAn! On Tue, 2 Jun 2026 at 19:50, Lucas Brutschy via dev <dev@kafka.apache.org> wrote: > > Thanks for managing the release PoAn! > > On Tue, Jun 2, 2026 at 5:46 PM Chia-Ping Tsai <chia7712@gmail.com> wrote: > > > > > > Thanks for PoAn to manage this release > > > > > sunil chaudhari <sunilmchaudhari05@gmail.com> 於 2026年6月2日 晚上11:23 寫道： > > > > > > Hi, > > > Thanks for announcement. > > > Are these changes available in 4.3.0 > > > We are setting up new cluster version 4.3.0. > > > Dont want to miss these bug fixes. > > > > > > Regards, > > > Sunil. > > > > > >> On Tue, 2 Jun 2026 at 7:41 PM, PoAn Yang <payang@apache.org> wrote: > > >> > > >> The Apache Kafka community is pleased to announce the release for Apache > > >> ...