Hi Peter,
Thanks, that's very helpful! We'll go on with upgrading to 2.4.1 and not
touching our ZK 3.4.6 for now. I can report back if that actually causes
issues just in case anybody is interested.

On Thu, Jul 23, 2020 at 2:00 PM Peter Bukowinski <pmb...@gmail.com> wrote:

> Agreed. We use a cloudera distribution of zookeeper, that is versioned at
> 3.4.5 (plus a bunch of backported patches) with kafka 2.4 and haven’t had
> any issues.
>
>
> > On Jul 23, 2020, at 1:19 PM, Andrey Klochkov <akloch...@liftoff.io>
> wrote:
> >
> > We are running a separate ZK cluster and its version is not really tied
> to
> > the version of Kafka we're using.
> >
> > I have seen the Confluent compatibility matrix and based on that our
> > *current* version of Kafka is not compatible with our version of ZK, and
> we
> > haven't seen any problems with that. My suspicion is that Confluent might
> > be using some of the newer ZK features such as e.g. dynamic
> > configuration and that's where their requirements come from, but that
> > doesn't mean Kafka requires the versions of ZK that Confluent lists as
> > required for the Confluent platform.
> >
> > On Thu, Jul 23, 2020 at 1:06 PM M. Manna <manme...@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> AFAIK, ZK is packed with Kafka. So if you upgrade to 2.4.1 you’ll get
> what
> >> is in 2.4.1.
> >>
> >> It’s a little different however, if you’re hosting ZK in a different
> host
> >> running independently of Kafka.
> >>
> >> What’s your situation ?
> >>
> >>
> >>
> >> On Thu, 23 Jul 2020 at 21:02, Andrey Klochkov <akloch...@liftoff.io>
> >> wrote:
> >>
> >>> Hello,
> >>> We're upgrading our Kafka from 1.1.0 to 2.4.1 and I'm wondering if ZK
> >> needs
> >>> to be upgraded too (we're currently on 3.4.6). The upgrade guide says
> >> that
> >>> "kafka has switched to the XXX version of ZK" but never says if
> switching
> >>> to a newer ZK is mandatory or not. What are the guidelines on keeping
> >> Kafka
> >>> and ZK compatible?
> >>>
> >>> --
> >>> Andrey Klochkov
> >>>
> >>
> >
> >
> > --
> > Andrey Klochkov
>
>

-- 
Andrey Klochkov

Reply via email to