Status

Current state:  Under DiscussionAccepted

Discussion thread: here

JIRA: here

...

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  Part#1 (blocking until commit) of this feature which add still an issue as it adds 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. 

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

...

• Reuse emit.checkpoints.enabled   and sync.group.offsets.enabled  and assume that if both are disabled then this feature needs to be fully disabled. I didn't want to relay rely on MirrorCheckpointConnector  configs to configure MirrorSourceConnector . And this might impact customers who enabled  MirrorSourceConnector  with intention to run MirrorCheckpointConnector  later in the future