Hey guys, this is because the configuration gets loaded into the internal
mm2-config topics, and these may get out of sync with the mm2.properties
file in some scenarios. I believe this occurs whenever an old/bad
configuration gets written to Kafka, which MM2 can read successfully but
which causes
Hi,
I have a similar issue. I changed the source cluster bootstrap address and
MM2 picked it up only partially. Some parts of it still use the old
address, some the new. The old and the new address list is routed to the
same cluster, same brokers, just on a different network path.
So is there an
