You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by pe...@apache.org on 2022/07/23 02:06:13 UTC
[pulsar] branch master updated: [doc][improvement] enable geo-replication at topic level need extra config (#16713)
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 162587b5768 [doc][improvement] enable geo-replication at topic level need extra config (#16713)
162587b5768 is described below
commit 162587b5768a34a7063080165044e2e121b0e907
Author: youzipi <bl...@qq.com>
AuthorDate: Sat Jul 23 10:06:05 2022 +0800
[doc][improvement] enable geo-replication at topic level need extra config (#16713)
---
site2/docs/administration-geo.md | 6 +++++-
site2/website/versioned_docs/version-2.10.0/administration-geo.md | 6 +++++-
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/site2/docs/administration-geo.md b/site2/docs/administration-geo.md
index 68ed9edab55..778b5f61137 100644
--- a/site2/docs/administration-geo.md
+++ b/site2/docs/administration-geo.md
@@ -143,7 +143,11 @@ $ bin/pulsar-admin topics set-replication-clusters --clusters us-west,us-east,us
- You can change the replication clusters for a namespace at any time, without disruption to ongoing traffic. Replication channels are immediately set up or stopped in all clusters as soon as the configuration changes.
- Once you create a geo-replication namespace, any topics that producers or consumers create within that namespace are replicated across clusters. Typically, each application uses the `serviceUrl` for the local cluster.
-
+- If you are using Pulsar version `2.10.x`, to enable geo-replication at topic level, you need to change the following configurations in the `conf/broker.conf` or `conf/standalone.conf` file to enable topic policies service.
+```shell
+systemTopicEnabled=true
+topicLevelPoliciesEnabled=true
+```
:::
### Use topics with geo-replication
diff --git a/site2/website/versioned_docs/version-2.10.0/administration-geo.md b/site2/website/versioned_docs/version-2.10.0/administration-geo.md
index 4f5b5565eca..2d64f0b643f 100644
--- a/site2/website/versioned_docs/version-2.10.0/administration-geo.md
+++ b/site2/website/versioned_docs/version-2.10.0/administration-geo.md
@@ -144,7 +144,11 @@ $ bin/pulsar-admin topics set-replication-clusters --clusters us-west,us-east,us
- You can change the replication clusters for a namespace at any time, without disruption to ongoing traffic. Replication channels are immediately set up or stopped in all clusters as soon as the configuration changes.
- Once you create a geo-replication namespace, any topics that producers or consumers create within that namespace are replicated across clusters. Typically, each application uses the `serviceUrl` for the local cluster.
-
+- If you are using Pulsar version `2.10.x`, to enable geo-replication at topic level, you need to change the following configurations in the `conf/broker.conf` or `conf/standalone.conf` file to enable topic policies service.
+```shell
+systemTopicEnabled=true
+topicLevelPoliciesEnabled=true
+```
:::
### Use topics with geo-replication