MirrorMaker 2 without write access on source

2022-01-18 Thread Ruben de Vries
We've been trying to setup a MirrorMaker 2 to mirror data from a cluster on which we only have read access. It seems to work, but the logs are hammered with TopicAuthorizationException errors in the MirrorCheckpointConnector thread for a mm2-offset-syncs.target-cluster.internal topic. At this poin

Re: [VOTE] 3.1.0 RC1

2022-01-18 Thread Jakub Scholz
+1 (non-binding). I used the staged Scala 2.13 binaries and the staging Maven repository to run my tests. All seems to work fine, no issues found. Thanks Jakub On Wed, Jan 12, 2022 at 1:59 PM David Jacot wrote: > Hello Kafka users, developers and client-developers, > > This is the second candid

Re: [VOTE] 3.1.0 RC1

2022-01-18 Thread Israel Ekpo
Performed the following validations using the tools available here: https://github.com/izzyacademy/apache-kafka-release-party - Verified signatures, keys and hashes for release artifacts - Deployed Multi-Node Cluster in Legacy Mode (with Zookeeper) - Deployed Multi-Node Cluster in KRaft

Re: MirrorMaker 2 without write access on source

2022-01-18 Thread Urbán Dániel
Hi Ruben, The offset-syncs topic is necessary when the checkpointing feature of MM2 is being used (a.k.a. consumer group offset replication). Since the offsets of the original and the replica topic are not guaranteed to exactly match, there has to be a translation step when replicating the com