...

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

One of MM2's main features is syncing consumer group offset between clusters. This feature relays relies on two separate connectors

...

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  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.

...

emit.offset-syncs.enabled is set to true by default so any existing customer or customers who use-cases or use-cases that run this feature will do nothing. Only customers who use-case that wish to fully disable this feature will need to set emit.offset-syncs.enabled to false.

...