You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm configuring Kafka replication using MirrorMaker 2 (MM2) across two Kubernetes clusters, A and B. Each cluster runs the Strimzi operator and a Kafka server.
I begin by deploying MM2 on cluster B to replicate data from A to B.
For a switchover:
Stop consumers on A.
Stop MM2 on B.
Deploy MM2 on A to replicate from B to A, using auto.offset.reset: latest.
Move consumers to B (my understanding here is that consumers will take it over from where they left of in A).
Later, I want to switch back:
Stop consumers on B.
Stop MM2 on A.
Deploy MM2 on B to replicate from A to B again.
At this point, MM2's internal topics on B may be outdated. Should I first remove the MM2 internal topics on B, or is there something I'm missing in my understanding?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm configuring Kafka replication using MirrorMaker 2 (MM2) across two Kubernetes clusters, A and B. Each cluster runs the Strimzi operator and a Kafka server.
I begin by deploying MM2 on cluster B to replicate data from A to B.
For a switchover:
Later, I want to switch back:
At this point, MM2's internal topics on B may be outdated. Should I first remove the MM2 internal topics on B, or is there something I'm missing in my understanding?
Beta Was this translation helpful? Give feedback.
All reactions