Hey Carl, that's what my team has done for our internal tooling, and I designed MirrorClient with that in mind. Given a single mm2.properties file you can create MirrorClients for each cluster and those in turn give you Admin/Consumer/Producer clients if you need them. Our internal tooling essentially looks for an mm2.properties file in a system-wide location and lets you interrogate any given cluster by alias, which is nice when you manage a very large number of Kafka clusters :)
Ryanne On Thu, Feb 27, 2020, 1:21 PM Carl Graving <cgrav...@gmail.com> wrote: > All: > I was tinkering around with the MirrorClient and was curious about the > configs. I see that I can use the MirrorMaker config to pull in the same > configs that were used to spin up the MM2 cluster. Seeing as MM2 is started > with these configs in a property file and it is passed in on command line, > I take it is implying that I should read the same file to set up my > MirrorClient application to then feed into MirrorMakerConfig, to the get > the clientConfig like in the code comments? Or am I reading too much into > this and just configure for the cluster I am setting up the Client for? > > thanks, > Carl >
