Prashanth created KAFKA-18995:
---------------------------------
Summary: MirrorMaker2 does not replicate from secondary to primary
DC
Key: KAFKA-18995
URL: https://issues.apache.org/jira/browse/KAFKA-18995
Project: Kafka
Issue Type: Bug
Components: mirrormaker
Affects Versions: 3.7.1
Reporter: Prashanth
I have a the following setup:
{+}Kafka cluster DC1{+}: TopicA
{+}Kafka cluster DC2{+}: DC1.TopicA (created by mirror maker in DC2)
A producer always runs in DC1. Consumer consumes and commits in DC1 up to 100
messages.
Consumer stops in DC1. Then it fails over to start in DC2. It now consumes and
commits in DC2 from topic DC1.TopicA in the same consumer group.
It consumes and commits 200 additional messages in DC2 from replicated topic
(DC1.TopicA). The consumer stops and fails back to DC1.
{*}The expectation is to start from message 301{*}. But this is not the case
(It starts from 101). The committed offsets in replicated topic never syncs
back to primary topic in the same consumer group (It used to work fine in
3.2.3).
I could not find a bug / feature reported along these lines hence I am flagging
it as a new one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
