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
Copy file name to clipboardExpand all lines: articles/hdinsight/kafka/apache-kafka-mirror-maker-2.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,12 @@ Learn how to use Apache Kafka's mirroring feature to replicate topics to a secon
14
14
In this article, you use mirroring to replicate topics between two HDInsight clusters. These clusters are in different virtual networks in different datacenters.
15
15
16
16
> [!NOTE]
17
-
> We can use mirroring cluster as a fault tolerance.
18
-
> This is valid only is primary cluster HDI Kafka 2.4.1, 3.2.0 and secondary cluster is HDI Kafka 3.2.0 versions.
19
-
> Secondary cluster would work seamlessly if your primary cluster went down.
20
-
> Consumer group offsets will be automatically translated to secondary cluster.
21
-
> Just point your primary cluster consumers to secondary cluster with same consumer group and your consumer group will start consuming from the offset where it left in primary cluster.
22
-
> The only difference would be that the topic name in backup cluster will change from TOPIC_NAME to primary-cluster-name.TOPIC_NAME.
17
+
> 1.We can use mirroring cluster as a fault tolerance.
18
+
> 2.This is valid only is primary cluster HDI Kafka 2.4.1, 3.2.0 and secondary cluster is HDI Kafka 3.2.0 versions.
19
+
> 3.Secondary cluster would work seamlessly if your primary cluster went down.
20
+
> 4.Consumer group offsets will be automatically translated to secondary cluster.
21
+
> 5.Just point your primary cluster consumers to secondary cluster with same consumer group and your consumer group will start consuming from the offset where it left in primary cluster.
22
+
> 6.The only difference would be that the topic name in backup cluster will change from TOPIC_NAME to primary-cluster-name.TOPIC_NAME.
0 commit comments