Page History

...

For use-cases where customers only run MM2 for replicating between clusters without the need for moving the consumer group offsets by running only MirrorSourceConnector. They still left with part#1 of this feature which add cost to the progress of their replication. The only workaround reducing the latency cost is by increasing offset.lag.max  to INT_MAX  which will result that the offset will never going to be queued for offset sync (Check `PartitionState::update` for details on how MM2 decided if it should emit an offset sync or not) however this doesn't eliminate the cost of creating an internal topic as it only will cause the offset for not been queued to beging with. 

This KIP propose that we add a new config for MirrorSourceConnector  to control enabling the offsets translation between clusters for replicated topics.

...