, Slawomir Kmiecik
> , Ricardo Antunes (WH Online)
>
> Subject: Re: [EXTERNAL] Re: Kafka upgrade recommendation
> Hey Wojciech,
> It has been a long time since we did the jump but we had waited until 3.3.x
> release when we did the jump and there were a lot of manual steps at tha
Date: Monday, 17 June 2024 at 14:16
To: us...@kafka.apache.org ,
kafka-clie...@googlegroups.com ,
dev@kafka.apache.org , Wojciech Frycz
Cc: Cezary Gajdzinski , Slawomir Kmiecik
, Ricardo Antunes (WH Online)
Subject: Re: [EXTERNAL] Re: Kafka upgrade recommendation
Hey Wojciech,
It has been a
t; ul. Kotlarska 11 | 31-539 Krakow
> From: Sejal Patel
> Date: Saturday, 15 June 2024 at 17:28
> To: us...@kafka.apache.org ,
> kafka-clie...@googlegroups.com ,
> dev@kafka.apache.org
> Cc: Cezary Gajdzinski , Wojciech Frycz
> , Slawomir Kmiecik
> , Ricardo Antunes (WH Onl
...@kafka.apache.org ,
kafka-clie...@googlegroups.com ,
dev@kafka.apache.org
Cc: Cezary Gajdzinski , Wojciech Frycz
, Slawomir Kmiecik
, Ricardo Antunes (WH Online)
Subject: [EXTERNAL] Re: Kafka upgrade recommendation
I would suggest going from 2.6.2 to 3.6.2 and then stopping and waiting until
I would suggest going from 2.6.2 to 3.6.2 and then stopping and waiting until
3.7.1 comes out. There is a pretty serious flaw in 3.7.0 that hit us and we
ended up having to downgrade to 3.6.2 to recover. The bug is fixed but not
going to be released until 3.7.1 comes out. The bug prevented metad
Hi there,
We have few clusters in AWS world and being forced to bump cluster version.
So, we are considering options to be in safer way possible, mitigating risks,
and without outage as possible (our business is 24/7).
Upgrade would be from 2.2.1 / 2.6.2 to 3.7.0 (MSK recommended version).
Thi
