KAFKA MM1.0 vs KAFKA MM2.0与汇合复制器与汇合群集链接

发布于 2025-01-26 08:08:16 字数 675 浏览 4 评论 0原文

我知道Apache Kafka MM1和Apache Kafka MM2之间有什么区别。

不支持主动设置和抵消同步

KAFKA MM1不支持MM1中的一个问题和更多使用irrirormaker 2.0

a- look-inside-kafka-kafka-mirrormaker-2

但我无法理解复制器和群集链接之间的差异。

I know what are differences between Apache Kafka MM1 and Apache Kafka MM2.

Kafka MM1 doesn't support Active-Active setup and Offset syncing in also an issue in MM1 and many more

Overview of Active-Active Kafka Cluster using MirrorMaker 2.0

a-look-inside-kafka-mirrormaker-2

But i am not able to understand the differences between Replicator and Cluster linking.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

稚然 2025-02-02 08:08:16

复制器是在MM2之前发布的,并提供了大多数相同的功能,但也可以复制主题配置,模式注册表详细信息和分区更改(我认为MM2不能这样做,MM1绝对没有)。

afaik,群集链接几乎就像“无服务器复制”;它不取决于运行/维护连接群集,因为我认为它直接在经纪人上运行,这也使其不像复制解决方案那样可扩展。与简单地启动/停止连接群集相比,它还需要重新启动经纪人启用/禁用。

Replicator was released before MM2 and offers most of the same features, but can also copy topic configurations, Schema Registry details, and partition changes (I don't think MM2 can do that, MM1 definitely does not).

AFAIK, cluster linking is almost like "serverless replication" ; it doesn't depend on running/maintaining a Connect cluster, as I believe it runs directly on the brokers, which also makes it not as scalable as a replication solution. It also requires restarting the brokers to enable/disable, as compared to simply starting/stopping a Connect cluster.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文