Nils, a REST API for MM2 was discussed at length, but so far the community hasn't settled on a plan. For now, if you need to monitor MM2's Connectors over HTTP, you can use a bunch of Connect clusters and manually configure them to run MirrorSourceConnector etc. This has some advantages, e.g. you can use the Connect REST API to start, stop, and re-configure individual connectors on-the-fly -- but it also means you have a lot of stuff to configure and monitor yourself.
I'd recommend monitoring MM2 via its JMX metrics and heartbeats. These provide substantially more information than the Connect REST API. Ryanne On Tue, Jan 14, 2020 at 9:32 AM Nils Hermansson < nils.hermans...@getdreams.com> wrote: > Another question is there anyway to open up a rest port like standard 8083 > when running > > ./bin/connect-mirror-maker.sh config/connect-mirror-maker.properties > > have tried adding rest.port=8083 but does not seem to work. > > Would like to be able to query the status of the connector via rest. > > On Tue, Jan 14, 2020 at 3:54 PM Nils Hermansson < > nils.hermans...@getdreams.com> wrote: > > > Hello, > > yes that seems todo the trick. > > > > Another questions is there any documentation somewhere describing how the > > offset translations topics MM2 creates actually works? > > We need to write code ourself until this PR is merged I guess. > > https://github.com/apache/kafka/pull/7577 > > > > > > Thanks for the help. > > > > On Tue, Jan 14, 2020 at 12:58 PM Karan Kumar <karankumar1...@gmail.com> > > wrote: > > > >> Hi Nils > >> > >> Can you try with the latest mm2 default config file found at > >> > >> > https://github.com/apache/kafka/blob/trunk/config/connect-mirror-maker.properties > >> . > >> Please feel free to reach out again if you are still stuck. > >> > >> Thanks > >> Karan > >> > >> > >> > >> On Tue, Jan 14, 2020 at 1:48 PM Nils Hermansson < > >> nils.hermans...@getdreams.com> wrote: > >> > >> > Hello, > >> > I am trying to setup a replication between 2 clusters with MM2. The > >> goal is > >> > to be able to disksnapshot the secondary cluster for backups hence we > >> only > >> > want one broker on the secondary cluster. It's very important for us > >> that > >> > we can replicate the offsets which MM2 should solve for us. > >> > > >> > Cluster: > >> > A=primary > >> > B=secondary > >> > > >> > Primary cluster have 3 brokers and secondary has one broker. > >> > > >> > My first attempt was as standalone worker. > >> > This attempt yielded replication of the topics but no topics for > offsets > >> > were created. > >> > MM2 configuration replication.factor = 1 was honored. > >> > > >> > Since I did not get any offsets in standalone mode I decided to test > >> > cluster mode. > >> > > >> > Secondary attempt was running MM2 in cluster mode(still one broker in > >> > secondary cluster) however the problem I get here is that MM2 tries to > >> > write the messages with a replication of 3 to the secondary cluster. > In > >> > this case MM2 seem to create the offset topics but fail when trying to > >> > create them. > >> > > >> > Giving: > >> > org.apache.kafka.connect.errors.ConnectException: Error while > >> attempting to > >> > create/find topic(s) 'mm2-offsets.A.internal' > >> > ... > >> > ... > >> > InvalidReplicationFactorException: Replication factor: 3 larger than > >> > available brokers: 1 > >> > ... > >> > > >> > I have tried setting these config value in the properties config but > >> they > >> > do not seem to be honored: > >> > replication.factor = 1 > >> > > >> > A.replication.factor = 1 > >> > B.replication.factor = 1 > >> > > >> > BR > >> > Nils > >> > > >> > >> > >> -- > >> Thanks > >> Karan > >> > > >
