This is an automated email from the ASF dual-hosted git repository.
penghui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new e6e63fb [Doc]--Update geo-replication doc. (#7218)
e6e63fb is described below
commit e6e63fbf3cc99484041c63965bacf9c5394cb064
Author: HuanliMeng <[email protected]>
AuthorDate: Wed Jun 10 07:07:43 2020 +0800
[Doc]--Update geo-replication doc. (#7218)
---
site2/docs/administration-geo.md | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/site2/docs/administration-geo.md b/site2/docs/administration-geo.md
index 6ab1730..3ca3ec9 100644
--- a/site2/docs/administration-geo.md
+++ b/site2/docs/administration-geo.md
@@ -35,8 +35,7 @@ In normal cases, when connectivity issues are none, messages
are replicated imme
Applications can create producers and consumers in any of the clusters, even
when the remote clusters are not reachable (like during a network partition).
-> #### Subscriptions are local to a cluster
-> While producers and consumers can publish to and consume from any cluster in
a Pulsar instance, subscriptions are local to the clusters in which the
subscriptions are created and cannot be transferred between clusters. If you do
need to transfer a subscription, you need to create a new subscription in the
desired cluster.
+Producers and consumers can publish messages to and consume messages from any
cluster in a Pulsar instance. However, subscriptions cannot only be local to
the cluster where the subscriptions are created but also can be transferred
between clusters after replicated subscription is enabled. Once replicated
subscription is enabled, you can keep subscription state in synchronization.
Therefore, a topic can be asynchronously replicated across multiple
geographical regions. In case of failover [...]
In the aforementioned example, the **T1** topic is replicated among three
clusters, **Cluster-A**, **Cluster-B**, and **Cluster-C**.
