Thank you Matthias. I will try and update here for others knowledge. On Wed, 11 Feb 2026 at 12:39 PM, Matthias J. Sax <[email protected]> wrote:
> Yes, should be possible. > > A clean rolling restart broker-by-broker with enough stabilization time > in between, should ensure that partition leader fail-over and clients > use the new leaders while a single broker is bounces, and should fail > back to the preferred leader after a broker got restarted. > > > -Matthias > > On 2/10/26 9:33 PM, sunil chaudhari wrote: > > Hello Kafka experts, > > Any comments on this please? > > > > Regards, > > Sunil. > > > > On Tue, 10 Feb 2026 at 10:25 PM, sunil chaudhari < > > [email protected]> wrote: > > > >> Hi Matthias, > >> Thanks for quick reply. > >> Little precise about my need… > >> I have 23 brokers in the confluent cluster. > >> I have 500+ filebeats running as producers in prod environment. All > >> filebeats have static broker hosts configured. Some have 3 brokers, > some 8 > >> some 12 and some has 23 brokers configured. > >> Also there are 70+ logstash as consumers. > >> All I want is… Switching off the confluent version on Zookeeper and > start > >> apache version(anything that can support confluent 7.7.2) on same hosts > >> same ports. ( Not sure about data path directory) > >> Same for all brokers in rolling fashion Not at once. > >> I dont want any downtime. 500+ filebeats and 70+ logstash shouldn’t > >> experience any downtime. > >> > >> is it possible? > >> > >> Regards, > >> Sunil. > >> > >> On Tue, 10 Feb 2026 at 9:44 PM, Matthias J. Sax <[email protected]> > wrote: > >> > >>>> OS apache kafka version 3.4 Or 3.5 is last > >>>>> version that supports zookeeper. > >>> > >>> That's not correct. Apache Kafka supports ZK up-to-including 3.9. > >>> > >>> Confluent 7.7 maps to Apache Kafka 3.7, Confluent guarantee that it's > >>> compatible is OSS Kafka. So switching to Apache Kafka 3.7 should not > >>> cause any issues. Of course, as always you might want to test this in a > >>> non-prov environment first. > >>> > >>> In any case, if you want to move to 4.x, you need to migrate off ZK > >>> first. It's recommended to upgrade to 3.9 first, as it's the most > stable > >>> release with respect to ZK to KRaft migration. Migration to KRaft would > >>> be the next step. And after you are on KRaft, upgrade to your desired > >>> 4.x version. > >>> > >>> Of course, it's also possible to skip the step to migrate to 3.9, and > >>> upgrade from 3.7 (with KRaft) to 4.x directly. > >>> > >>> > >>> -Matthias > >>> > >>> > >>> > >>> On 2/10/26 7:22 AM, sunil chaudhari wrote: > >>>> Hi , > >>>> > >>>> Any kafka admin to help here and tell me migration path for this > >>> version. I > >>>> have confluent-7.7.2 running with Zookeeper. I have to move to Open > >>> source > >>>> Apache Kafka 4.0 or above. OS apache kafka version 3.4 Or 3.5 is last > >>>> version that supports zookeeper. Give me migration path so that I > move > >>>> form "confluent-7.72 with Zookeeper" to OS apache Kafka 4.0 or Above > >>> with > >>>> KRaft Controllers. > >>>> > >>>> What if I move from Zookeeper to Kraft in Confluent 7.7.2 then I do > >>> Inplace > >>>> upgrade to OS apache kafka 3.5 or 3.4? Here I can get rid of > >>> Confluent. And > >>>> then I upgrade to 4.0 Open Source version. > >>>> > >>>> Is there any risk if metadata in Confluent not match with metadata in > >>>> apache kafka. ? > >>>> > >>>> Regards, > >>>> > >>>> Sunil. > >>>> > >>> > >>> > > > >
