This is an automated email from the ASF dual-hosted git repository.
lhotari 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 6e0a2a4956fb Solves apache/pulsar/issues/22848 (#909)
6e0a2a4956fb is described below
commit 6e0a2a4956fb052a685f3b873459d3908e2dabc4
Author: Alvaro <[email protected]>
AuthorDate: Wed Jun 5 12:45:27 2024 +0200
Solves apache/pulsar/issues/22848 (#909)
Add information to unload the topic when you execute an earliest
replication
As mentioned in motivation of
[PIP-356](https://github.com/apache/pulsar/blob/master/pip/pip-356.md#motivation)
---
docs/administration-geo.md | 2 +-
versioned_docs/version-3.0.x/administration-geo.md | 2 +-
versioned_docs/version-3.1.x/administration-geo.md | 2 +-
versioned_docs/version-3.2.x/administration-geo.md | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/administration-geo.md b/docs/administration-geo.md
index aa54e5d34ee4..575d92610c2c 100644
--- a/docs/administration-geo.md
+++ b/docs/administration-geo.md
@@ -275,6 +275,6 @@ Using geo-replication to migrate data between clusters is a
special use case of
:::note
* The replication starts from step 4, which means existing messages in your
old cluster are not replicated.
-* If you have some older messages to migrate, you can pre-create the
replication subscriptions for each topic and set it at the earliest position by
using `pulsar-admin topics create-subscription -s pulsar.repl.new-cluster -m
earliest <topic>`.
+* If you have some older messages to migrate, you can pre-create the
replication subscriptions for each topic and set it at the earliest position by
using `pulsar-admin topics create-subscription -s pulsar.repl.new-cluster -m
earliest <topic>`. Until
[PIP-356](https://github.com/apache/pulsar/blob/master/pip/pip-356.md) is
merged you will need to unload the topic to start georeplication.
:::
diff --git a/versioned_docs/version-3.0.x/administration-geo.md
b/versioned_docs/version-3.0.x/administration-geo.md
index 9be134cf196e..53043ba68b16 100644
--- a/versioned_docs/version-3.0.x/administration-geo.md
+++ b/versioned_docs/version-3.0.x/administration-geo.md
@@ -281,6 +281,6 @@ Using geo-replication to migrate data between clusters is a
special use case of
:::note
* The replication starts from step 4, which means existing messages in your
old cluster are not replicated.
-* If you have some older messages to migrate, you can pre-create the
replication subscriptions for each topic and set it at the earliest position by
using `pulsar-admin topics create-subscription -s pulsar.repl.new-cluster -m
earliest <topic>`.
+* If you have some older messages to migrate, you can pre-create the
replication subscriptions for each topic and set it at the earliest position by
using `pulsar-admin topics create-subscription -s pulsar.repl.new-cluster -m
earliest <topic>`. Until
[PIP-356](https://github.com/apache/pulsar/blob/master/pip/pip-356.md) is
merged you will need to unload the topic to start georeplication.
:::
diff --git a/versioned_docs/version-3.1.x/administration-geo.md
b/versioned_docs/version-3.1.x/administration-geo.md
index 8f3cd0aa31c8..798db7d494b9 100644
--- a/versioned_docs/version-3.1.x/administration-geo.md
+++ b/versioned_docs/version-3.1.x/administration-geo.md
@@ -274,6 +274,6 @@ Using geo-replication to migrate data between clusters is a
special use case of
:::note
* The replication starts from step 4, which means existing messages in your
old cluster are not replicated.
-* If you have some older messages to migrate, you can pre-create the
replication subscriptions for each topic and set it at the earliest position by
using `pulsar-admin topics create-subscription -s pulsar.repl.new-cluster -m
earliest <topic>`.
+* If you have some older messages to migrate, you can pre-create the
replication subscriptions for each topic and set it at the earliest position by
using `pulsar-admin topics create-subscription -s pulsar.repl.new-cluster -m
earliest <topic>`. Then you will need to unload the topic to start
georeplication.
:::
diff --git a/versioned_docs/version-3.2.x/administration-geo.md
b/versioned_docs/version-3.2.x/administration-geo.md
index aa54e5d34ee4..575d92610c2c 100644
--- a/versioned_docs/version-3.2.x/administration-geo.md
+++ b/versioned_docs/version-3.2.x/administration-geo.md
@@ -275,6 +275,6 @@ Using geo-replication to migrate data between clusters is a
special use case of
:::note
* The replication starts from step 4, which means existing messages in your
old cluster are not replicated.
-* If you have some older messages to migrate, you can pre-create the
replication subscriptions for each topic and set it at the earliest position by
using `pulsar-admin topics create-subscription -s pulsar.repl.new-cluster -m
earliest <topic>`.
+* If you have some older messages to migrate, you can pre-create the
replication subscriptions for each topic and set it at the earliest position by
using `pulsar-admin topics create-subscription -s pulsar.repl.new-cluster -m
earliest <topic>`. Until
[PIP-356](https://github.com/apache/pulsar/blob/master/pip/pip-356.md) is
merged you will need to unload the topic to start georeplication.
:::
