Hello All, MirrorMaker 2.0 <https://cwiki.apache.org/confluence/display/KAFKA/KIP-382%3A+MirrorMaker+2.0> (MM 2.0) is a new Kafka community initiative that is designed to address the limitations of current MirrorMaker.
The offset translation is one of MM2.0's features to serve the foundation of migrating or failing over downstream consumers (including Kafka stream applications) from the primary to the backup cluster, as the consumers will use the translated offsets to resume the consumption from where they left off at the primary cluster, without losing messages or consuming many duplicate messages. To achieve a smooth and transparent migration, there are two important steps: (1) consumer offsets can be translated into the ones that make sense in another cluster, which is already done by the current MM 2.0. (2) periodically synchronize the translated offsets to the *__consumer_offsets* topic, so that when the consumers switch over to the other cluster, they can immediately start off from the last known and translated offsets. This KIP is mostly to propose (2) as a new feature, called "automated consumer offset sync across clusters" in MM 2.0, and discuss the initial design and how the interface looks like. This is a small KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-545%3A+support+automated+consumer+offset+sync+across+clusters+in+MM+2.0 since it add a new configuration in public interface PR: https://issues.apache.org/jira/browse/KAFKA-9076 >From the comments of PR, the author of MM 2.0 is already onboard this proposal. Please take a look and I would like to hear feedback. Thanks, Ning
