Any idea how much time you will need Mickael?
Personally, I would like to move fast, and delaying the release for an
uncertain amount of time seems not desirable. We will do a 4.1.2 release
for sure some time later.
But I understand that it's a critical issue for Connect, so I agree that
it would be great to get into 4.1.1. (Or as a last resort, so a quick
4.1.2 after you figured out a fix, in case you need more time...)
@Lianet: Thanks for volunteering to be the RM! Can you prepare a release
plan?
-Matthias
On 10/7/25 9:42 AM, Mickael Maison wrote:
Hi,
If we do a 4.1.1 I'd like to include
https://issues.apache.org/jira/browse/KAFKA-19758.
I'm still investigating but it looks like KIP-891 broke plugin
isolation in Connect and thus workloads that worked with Connect 4.0.0
don't work anymore on 4.1.0.
Thanks,
Mickael
On Mon, Oct 6, 2025 at 3:54 PM Chia-Ping Tsai <[email protected]> wrote:
+1 to release 4.1.1 ASAP
Lianet M. <[email protected]> 於 2025年10月6日 週一 下午9:33寫道：
Hello,
Agree with the proposed 4.1.1 bug fix release to ship this asap. If we all
agree on the need for it, I would like to volunteer to be the release
manager.
Best,
Lianet
On Fri, Oct 3, 2025 at 5:44 PM Matthias J. Sax <[email protected]> wrote:
Hello,
we now understand the recently reported memory leak bug in Kafka Streams
4.1.0, and have a PR to fix it.
https://issues.apache.org/jira/browse/KAFKA-19748
I consider this bug severe, as we expect that it affects a large number
of Kafka Streams user, makes Kafka Streams unusable, and there is no
workaround.
So I would like to propose to start 4.1.1 bug-fix release immediately,
and also update the Kafka web page with a note that people should be
careful and maybe not even upgrade to Kafka Streams 4.1.0.
Looking forward to your feedback.
-Matthias
