This is an automated email from the ASF dual-hosted git repository.
liuyu pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 0ab4daf8ece [improve][doc] Subscription replication doesn't replicate
the type (#625)
0ab4daf8ece is described below
commit 0ab4daf8ecef674bd69a5d9eff125eb62a6e429c
Author: Alvaro <[email protected]>
AuthorDate: Wed Jul 5 03:57:02 2023 +0200
[improve][doc] Subscription replication doesn't replicate the type (#625)
---
versioned_docs/version-3.0.x/administration-geo.md | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/versioned_docs/version-3.0.x/administration-geo.md
b/versioned_docs/version-3.0.x/administration-geo.md
index cedf535b4fe..48344aa041f 100644
--- a/versioned_docs/version-3.0.x/administration-geo.md
+++ b/versioned_docs/version-3.0.x/administration-geo.md
@@ -227,6 +227,12 @@ If you want to use replicated subscriptions in Pulsar:
.replicateSubscriptionState(true)
.subscribe();
```
+:::note
+
+* Subscription type is not replicated between clusters. However, it's
determined by the first consumer that connects to the subscription.
+
+:::
+
### Advantages
@@ -240,6 +246,7 @@ If you want to use replicated subscriptions in Pulsar:
* When you enable replicated subscriptions, you're creating a consistent
distributed snapshot to establish an association between message ids from
different clusters. The snapshots are taken periodically. The default value is
`1 second`. It means that a consumer failing over to a different cluster can
potentially receive 1 second of duplicates. You can also configure the
frequency of the snapshot in the `broker.conf` file.
* Only the base line cursor position is synced in replicated subscriptions
while the individual acknowledgments are not synced. This means the messages
acknowledged out-of-order could end up getting delivered again, in the case of
a cluster failover.
+
## Migrate data between clusters using geo-replication
Using geo-replication to migrate data between clusters is a special use case
of the [active-active replication
pattern](concepts-replication.md#active-active-replication) when you don't have
a large amount of data.
