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 have two Kafka clusters with MirrorMaker2 configured in an active/passive setup. During the switchover operation, I scale down MirrorMaker2 on the active cluster, while on the other cluster, I remove any internal topics and scale up MirrorMaker2.
What I don't understand is why heartbeats topic is created under a different name, such as "source.heartbeats", when the "heartbeats" topic exists on the active cluster. Additionally, after I perform another switchover, I end up with another topic called "source.source.heartbeats".
Is there a way to solve this problem in an easy way, like configuration? For the other topics, I do not see such behaviour.
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
Uh oh!
There was an error while loading. Please reload this page.
-
I have two Kafka clusters with MirrorMaker2 configured in an active/passive setup. During the switchover operation, I scale down MirrorMaker2 on the active cluster, while on the other cluster, I remove any internal topics and scale up MirrorMaker2.
What I don't understand is why heartbeats topic is created under a different name, such as "source.heartbeats", when the "heartbeats" topic exists on the active cluster. Additionally, after I perform another switchover, I end up with another topic called "source.source.heartbeats".
Is there a way to solve this problem in an easy way, like configuration? For the other topics, I do not see such behaviour.
Beta Was this translation helpful? Give feedback.
All reactions