MM2 setup using Kafka 2.4 compatibility with Kafka Broker built using 2.0.0 ver.

[Ranga <ra...@gmail.com>]

Hi Kakfa Experts

Trying to understand compatibility of MM2 libraries packaged as part of
core kafka release 2.4 with Kafka Cluster running with Kafka core version
2.0.0.

The major improvements to MM2 were implemented as part of the KIP-382
<https://cwiki.apache.org/confluence/display/KAFKA/KIP-382%3A+MirrorMaker+2.0>
and
merged via this PR <https://github.com/apache/kafka/pull/6295/files>. In
this PR I don’t see any changes being made to core kafka. The changes are
only seen with Kafka-connect and mirrormaker related code.

As I know Kafka Connect is a client application to kafka (Similar to any
standard consumer and producer application). And MM2 built on top of Kafka
Connect Architecture.

Though MirrorMaker2 related libraries are bundled with Core kafka libraries
i.e., 2.4 Kafka version as part of release cycles and packages, I think MM2
doesn't have absolute dependency on the same version of the Kafka Broker
(i.e., the one built with kafka 2.4.).

The reason being the MM2 component is client side.

Is it valid to assume that we can set MM2 using kafka core 2.4 release
packages to work with Kafka Broker set up with Kafka 2.0.0?

Any responses, comments or any materials in this regard are highly
appreciated.


Many thanks in advance!


-- 
Thanks & Regards
Ranga

Re: MM2 setup using Kafka 2.4 compatibility with Kafka Broker built using 2.0.0 ver.

[Ryanne Dolan <ry...@gmail.com>]

Ranga, yes that will work. You are correct that mm2's compatibility matrix
is essentially the same as the client's. I've tested 2.4 mm2 against 0.10.2
brokers and it works fine. Anything older than that may still generally
work, but you may see errors for unsupported apis.

Ryanne

On Mon, Feb 7, 2022, 9:58 AM Ranga <ra...@gmail.com> wrote:

> Hi Kakfa Experts
>
> Trying to understand compatibility of MM2 libraries packaged as part of
> core kafka release 2.4 with Kafka Cluster running with Kafka core version
> 2.0.0.
>
> The major improvements to MM2 were implemented as part of the KIP-382
> <
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-382%3A+MirrorMaker+2.0
> >
> and
> merged via this PR <https://github.com/apache/kafka/pull/6295/files>. In
> this PR I don’t see any changes being made to core kafka. The changes are
> only seen with Kafka-connect and mirrormaker related code.
>
> As I know Kafka Connect is a client application to kafka (Similar to any
> standard consumer and producer application). And MM2 built on top of Kafka
> Connect Architecture.
>
> Though MirrorMaker2 related libraries are bundled with Core kafka libraries
> i.e., 2.4 Kafka version as part of release cycles and packages, I think MM2
> doesn't have absolute dependency on the same version of the Kafka Broker
> (i.e., the one built with kafka 2.4.).
>
> The reason being the MM2 component is client side.
>
> Is it valid to assume that we can set MM2 using kafka core 2.4 release
> packages to work with Kafka Broker set up with Kafka 2.0.0?
>
> Any responses, comments or any materials in this regard are highly
> appreciated.
>
>
> Many thanks in advance!
>
>
> --
> Thanks & Regards
> Ranga
>

Re: MM2 setup using Kafka 2.4 compatibility with Kafka Broker built using 2.0.0 ver.

[Ryanne Dolan <ry...@gmail.com>]

Ranga, yes that will work. You are correct that mm2's compatibility matrix
is essentially the same as the client's. I've tested 2.4 mm2 against 0.10.2
brokers and it works fine. Anything older than that may still generally
work, but you may see errors for unsupported apis.

Ryanne

On Mon, Feb 7, 2022, 9:58 AM Ranga <ra...@gmail.com> wrote:

> Hi Kakfa Experts
>
> Trying to understand compatibility of MM2 libraries packaged as part of
> core kafka release 2.4 with Kafka Cluster running with Kafka core version
> 2.0.0.
>
> The major improvements to MM2 were implemented as part of the KIP-382
> <
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-382%3A+MirrorMaker+2.0
> >
> and
> merged via this PR <https://github.com/apache/kafka/pull/6295/files>. In
> this PR I don’t see any changes being made to core kafka. The changes are
> only seen with Kafka-connect and mirrormaker related code.
>
> As I know Kafka Connect is a client application to kafka (Similar to any
> standard consumer and producer application). And MM2 built on top of Kafka
> Connect Architecture.
>
> Though MirrorMaker2 related libraries are bundled with Core kafka libraries
> i.e., 2.4 Kafka version as part of release cycles and packages, I think MM2
> doesn't have absolute dependency on the same version of the Kafka Broker
> (i.e., the one built with kafka 2.4.).
>
> The reason being the MM2 component is client side.
>
> Is it valid to assume that we can set MM2 using kafka core 2.4 release
> packages to work with Kafka Broker set up with Kafka 2.0.0?
>
> Any responses, comments or any materials in this regard are highly
> appreciated.
>
>
> Many thanks in advance!
>
>
> --
> Thanks & Regards
> Ranga
>