Kafka

The Apache Kafka community is pleased to announce the release for Apache Kafka 4.2.0 This release has many exciting changes: * Kafka Queues (Share Groups) is now production-ready with new features like the RENEW acknowledgement type for extended processing times, adaptive batching for share coordinators, soft and strict enforcements of quantity of fetched records, and comprehensive lag metrics. * Kafka Streams brings the server-side rebalance protocol to GA with a limited feature set, adds dead letter queue support in exception handlers, introduces anchored wall-clock punctuation for deterministic scheduling, and gives users full control over whether to send a leave group request on closing. * This release also delivers significant improvements to consistency and observability: CLI tools now feature standardized arguments like –bootstrap-server across all tools, metric naming has been corrected to follow the kafka.COMPONENT convention, and new idle ratio metrics pr...

Hi Avishek Das: Though I am not sure about your issue. but I encounter the similar issue and fix it with: https://github.com/apache/kafka/pull/20007 https://github.com/apache/kafka/pull/20203 https://cwiki.apache.org/confluence/x/Hg9JFg You can refer to it to see if it is the same issue. thanks Regards Jian Avishek Das via users < users@kafka.apache.org > 于2026年2月16日周一 21:32写道： > Hello Team, > > During tiered storage performance testing on Kafka 3.9.1, we observed cases > where a broker did not trigger scheduled RLMCopy tasks, resulting in no > segment uploads to remote storage. Scenarios observed: > > - During a rolling restart while tiered storage was actively copying > segments, one broker (out of six) stopped copying segments after > restart. > > - After multiple rolling restarts before enabling tiered storage at > topic level, enabling tiered storage again caused one broker (out of > six...

Hi Anand, The partitionsFor API does not guarantee that a single call will return the data if the topic does not exist. It issues a first metadata request to create the topic, and waits for the api timeout for a response (timeout param or default.api.timeout.ms config). Then returns whatever it gets from the broker in that single call (empty if the topic is not found within the timeout, described in the java docs https://github.com/apache/kafka/blob/e678b4bb7ca99c7d1be0d554ffe7e66f584771d6/clients/src/main/java/org/apache/kafka/clients/consumer/KafkaConsumer.java#L1415 ). Also there are old integration tests with the pattern you describe: a first call to ensure topic is created, then a following one expected to retrieve the partitions for the topic (e.g, in 3.9 branch https://github.com/apache/kafka/blob/5e9866f43ab8e7e41ef39e5584ac50019381328d/core/src/test/scala/integration/kafka/api/PlaintextConsumerTest.scala#L176 ) That being said, I wonder if the difference you...

Hello Team, During tiered storage performance testing on Kafka 3.9.1, we observed cases where a broker did not trigger scheduled RLMCopy tasks, resulting in no segment uploads to remote storage. Scenarios observed: - During a rolling restart while tiered storage was actively copying segments, one broker (out of six) stopped copying segments after restart. - After multiple rolling restarts before enabling tiered storage at topic level, enabling tiered storage again caused one broker (out of six) to stop copying segments. In both cases, restarting the affected broker resolved the issue and copying resumed. DEBUG logging showed that RLMCopy tasks were created for leader partitions, traffic was active, and rolled segments were available. However, no debug logs appeared from the actual copy path < https://github.com/apache/kafka/blob/3.9/core/src/main/java/kafka/log/remote/RemoteLogManager.java#L839 >, suggesting the copy workflow was not being tri...

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? Regards, Apoorva Maheshwari From: Apoorva Maheshwari Sent: 13 February 2026 11:10 To: ' users-subscribe@kafka.apache.org ' < users-subscribe@kafka.apache.org >; ' users@kafka.apache.org ' < users@kafka.apache.org > Cc: Abhishek Kant Rattan < abhishek.kant.rattan@ericsson.com >; Sahil Sharma D < sahil.d.sharma@ericsson.com > Subject: RE: Version info that supports Jetty v12.0.25 Response awaited. Regards, Apoorva Maheshwari From: Apoorva Maheshwari Sent: 11 February 2026 10:30 To: users-subscribe@kafka.apache.org <mailto: users-subscribe@kafka.apache.org >; users@kafka.apache.org <mailto: users@kafka.apache.org > Cc: Abhishek Kant Rattan < abhishek.kant.rattan@ericsson.com <mailto: abhishek.kant.rattan@ericsson.com >>; S...

I had responded, and please check https://issues.apache.org/jira/browse/KAFKA-20168 On 2026/02/13 05:39:51 Apoorva Maheshwari via users wrote: > Response awaited. > > Regards, > Apoorva Maheshwari > > From: Apoorva Maheshwari > Sent: 11 February 2026 10:30 > To: users-subscribe@kafka.apache.org ; users@kafka.apache.org > Cc: Abhishek Kant Rattan < abhishek.kant.rattan@ericsson.com >; Sahil Sharma D < sahil.d.sharma@ericsson.com > > Subject: Version info that supports Jetty v12.0.25 > > Hello Team, > > Please confirm your plan to release a version that supports Jetty v12.0.25, in order to address Jetty CVE-2025-5115. > > Regards, > Apoorva Maheshwari > > >

Response awaited. Regards, Apoorva Maheshwari From: Apoorva Maheshwari Sent: 11 February 2026 10:30 To: users-subscribe@kafka.apache.org ; users@kafka.apache.org Cc: Abhishek Kant Rattan < abhishek.kant.rattan@ericsson.com >; Sahil Sharma D < sahil.d.sharma@ericsson.com > Subject: Version info that supports Jetty v12.0.25 Hello Team, Please confirm your plan to release a version that supports Jetty v12.0.25, in order to address Jetty CVE-2025-5115. Regards, Apoorva Maheshwari