This is an automated email from the ASF dual-hosted git repository.
urfree 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 65643b9a174 Docs sync done from apache/pulsar(#84fecf1)
65643b9a174 is described below
commit 65643b9a1743ad90f856d8a78266666adf8a82a5
Author: Pulsar Site Updater <[email protected]>
AuthorDate: Fri May 20 10:30:21 2022 +0000
Docs sync done from apache/pulsar(#84fecf1)
---
site2/website-next/docs/concepts-messaging.md | 1 +
site2/website-next/docs/tiered-storage-overview.md | 17 ++++++++++-------
.../version-2.1.1-incubating/administration-geo.md | 17 -----------------
.../version-2.10.0/tiered-storage-filesystem.md | 1 +
.../version-2.10.0/tiered-storage-overview.md | 11 ++++++-----
.../versioned_docs/version-2.2.0/administration-geo.md | 17 -----------------
.../versioned_docs/version-2.2.1/administration-geo.md | 17 -----------------
.../versioned_docs/version-2.3.0/administration-geo.md | 17 -----------------
.../versioned_docs/version-2.3.1/administration-geo.md | 17 -----------------
.../version-2.7.0/tiered-storage-overview.md | 5 +++--
.../version-2.7.2/tiered-storage-overview.md | 5 +++--
.../version-2.7.3/tiered-storage-overview.md | 5 +++--
.../version-2.7.4/tiered-storage-overview.md | 5 +++--
.../version-2.8.0/tiered-storage-overview.md | 5 +++--
.../version-2.8.1/tiered-storage-overview.md | 5 +++--
.../version-2.8.2/tiered-storage-overview.md | 9 +++++----
.../version-2.8.3/tiered-storage-overview.md | 9 +++++----
.../version-2.9.0/tiered-storage-overview.md | 11 ++++++-----
.../versioned_docs/version-2.9.1/administration-geo.md | 17 -----------------
.../version-2.9.1/tiered-storage-overview.md | 9 +++++----
.../versioned_docs/version-2.9.2/administration-geo.md | 17 -----------------
.../version-2.9.2/tiered-storage-overview.md | 11 ++++++-----
22 files changed, 63 insertions(+), 165 deletions(-)
diff --git a/site2/website-next/docs/concepts-messaging.md
b/site2/website-next/docs/concepts-messaging.md
index f7df3250762..b3520d70e8b 100644
--- a/site2/website-next/docs/concepts-messaging.md
+++ b/site2/website-next/docs/concepts-messaging.md
@@ -76,6 +76,7 @@ Access mode | Description
:-----------|------------
`Shared` | Multiple producers can publish on a topic. <br /><br
/>This is the **default** setting.
`Exclusive` | Only one producer can publish on a topic. <br /><br />If
there is already a producer connected, other producers trying to publish on
this topic get errors immediately.<br /><br />The “old” producer is evicted and
a “new” producer is selected to be the next exclusive producer if the “old”
producer experiences a network partition with the broker.
+`ExclusiveWithFencing`|Only one producer can publish on a topic. <br /><br
/>If there is already a producer connected, it will be removed and invalidated
immediately.
`WaitForExclusive` | If there is already a producer connected, the producer
creation is pending (rather than timing out) until the producer gets the
`Exclusive` access.<br /><br />The producer that succeeds in becoming the
exclusive one is treated as the leader. Consequently, if you want to implement
a leader election scheme for your application, you can use this access mode.
Note that the leader pattern scheme mentioned refers to using Pulsar as a
Write-Ahead Log (WAL) which means the l [...]
:::note
diff --git a/site2/website-next/docs/tiered-storage-overview.md
b/site2/website-next/docs/tiered-storage-overview.md
index b9e71e04836..1c58eafcba7 100644
--- a/site2/website-next/docs/tiered-storage-overview.md
+++ b/site2/website-next/docs/tiered-storage-overview.md
@@ -8,16 +8,19 @@ Pulsar's **Tiered Storage** feature allows older backlog data
to be moved from B
* Tiered storage uses [Apache jclouds](https://jclouds.apache.org) to support
[Amazon S3](https://aws.amazon.com/s3/), [GCS (Google Cloud
Storage)](https://cloud.google.com/storage/),
[Azure](https://azure.microsoft.com/en-us/services/storage/blobs/) and [Aliyun
OSS](https://www.aliyun.com/product/oss) for long term storage.
- With jclouds, it is easy to add support for more [cloud storage
providers](https://jclouds.apache.org/reference/providers/#blobstore-providers)
in the future.
+ With jclouds, it is easy to add support for more [cloud storage
providers](https://jclouds.apache.org/reference/providers/#blobstore-providers)
in the future.
- :::tip
+ :::tip
- For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
- For more information about how to use the Azure offloader with Pulsar, see
[here](tiered-storage-azure).
- For more information about how to use the Aliyun OSS offloader with
Pulsar, see [here](tiered-storage-aliyun).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+
+ - For more information about how to use the Azure offloader with Pulsar, see
[here](tiered-storage-azure).
+
+ - For more information about how to use the Aliyun OSS offloader with
Pulsar, see [here](tiered-storage-aliyun).
- :::
+ :::
* Tiered storage uses [Apache Hadoop](http://hadoop.apache.org/) to support
filesystems for long term storage.
diff --git
a/site2/website-next/versioned_docs/version-2.1.1-incubating/administration-geo.md
b/site2/website-next/versioned_docs/version-2.1.1-incubating/administration-geo.md
index c4463fb1205..78f72e1832e 100644
---
a/site2/website-next/versioned_docs/version-2.1.1-incubating/administration-geo.md
+++
b/site2/website-next/versioned_docs/version-2.1.1-incubating/administration-geo.md
@@ -129,23 +129,6 @@ $ bin/pulsar-admin namespaces set-clusters
my-tenant/my-namespace \
```
-#### Enable geo-replication at topic level
-
-You can set geo-replication at topic level using the command `pulsar-admin
topics set-replication-clusters`. For the latest and complete information about
`Pulsar admin`, including commands, flags, descriptions, and more information,
see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
-
-```shell
-
-$ bin/pulsar-admin topics set-replication-clusters --clusters
us-west,us-east,us-cent my-tenant/my-namespace/my-topic
-
-```
-
-:::tip
-
-- 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.
-
-:::
-
### Use topics with geo-replication
#### Selective replication
diff --git
a/site2/website-next/versioned_docs/version-2.10.0/tiered-storage-filesystem.md
b/site2/website-next/versioned_docs/version-2.10.0/tiered-storage-filesystem.md
index 70fe68d5268..4586bdf8b7e 100644
---
a/site2/website-next/versioned_docs/version-2.10.0/tiered-storage-filesystem.md
+++
b/site2/website-next/versioned_docs/version-2.10.0/tiered-storage-filesystem.md
@@ -123,6 +123,7 @@ You can configure the filesystem offloader driver in the
`broker.conf` or `stand
<TabItem value="NFS">
- **Required** configurations are as below.
+
Parameter | Description | Example value
|---|---|---
`managedLedgerOffloadDriver` | Offloader driver name, which is
case-insensitive. | filesystem
diff --git
a/site2/website-next/versioned_docs/version-2.10.0/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.10.0/tiered-storage-overview.md
index 9b7291b843e..7c6528ce2b3 100644
---
a/site2/website-next/versioned_docs/version-2.10.0/tiered-storage-overview.md
+++
b/site2/website-next/versioned_docs/version-2.10.0/tiered-storage-overview.md
@@ -9,14 +9,15 @@ Pulsar's **Tiered Storage** feature allows older backlog data
to be moved from B
* Tiered storage uses [Apache jclouds](https://jclouds.apache.org) to support
[Amazon S3](https://aws.amazon.com/s3/) and [GCS (Google Cloud
Storage)](https://cloud.google.com/storage/) for long term storage.
- With jclouds, it is easy to add support for more [cloud storage
providers](https://jclouds.apache.org/reference/providers/#blobstore-providers)
in the future.
+ With jclouds, it is easy to add support for more [cloud storage
providers](https://jclouds.apache.org/reference/providers/#blobstore-providers)
in the future.
- :::tip
+ :::tip
- For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
- :::
+ :::
* Tiered storage uses [Apache Hadoop](http://hadoop.apache.org/) to support
filesystems for long term storage.
diff --git
a/site2/website-next/versioned_docs/version-2.2.0/administration-geo.md
b/site2/website-next/versioned_docs/version-2.2.0/administration-geo.md
index c4463fb1205..78f72e1832e 100644
--- a/site2/website-next/versioned_docs/version-2.2.0/administration-geo.md
+++ b/site2/website-next/versioned_docs/version-2.2.0/administration-geo.md
@@ -129,23 +129,6 @@ $ bin/pulsar-admin namespaces set-clusters
my-tenant/my-namespace \
```
-#### Enable geo-replication at topic level
-
-You can set geo-replication at topic level using the command `pulsar-admin
topics set-replication-clusters`. For the latest and complete information about
`Pulsar admin`, including commands, flags, descriptions, and more information,
see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
-
-```shell
-
-$ bin/pulsar-admin topics set-replication-clusters --clusters
us-west,us-east,us-cent my-tenant/my-namespace/my-topic
-
-```
-
-:::tip
-
-- 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.
-
-:::
-
### Use topics with geo-replication
#### Selective replication
diff --git
a/site2/website-next/versioned_docs/version-2.2.1/administration-geo.md
b/site2/website-next/versioned_docs/version-2.2.1/administration-geo.md
index c4463fb1205..78f72e1832e 100644
--- a/site2/website-next/versioned_docs/version-2.2.1/administration-geo.md
+++ b/site2/website-next/versioned_docs/version-2.2.1/administration-geo.md
@@ -129,23 +129,6 @@ $ bin/pulsar-admin namespaces set-clusters
my-tenant/my-namespace \
```
-#### Enable geo-replication at topic level
-
-You can set geo-replication at topic level using the command `pulsar-admin
topics set-replication-clusters`. For the latest and complete information about
`Pulsar admin`, including commands, flags, descriptions, and more information,
see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
-
-```shell
-
-$ bin/pulsar-admin topics set-replication-clusters --clusters
us-west,us-east,us-cent my-tenant/my-namespace/my-topic
-
-```
-
-:::tip
-
-- 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.
-
-:::
-
### Use topics with geo-replication
#### Selective replication
diff --git
a/site2/website-next/versioned_docs/version-2.3.0/administration-geo.md
b/site2/website-next/versioned_docs/version-2.3.0/administration-geo.md
index c4463fb1205..78f72e1832e 100644
--- a/site2/website-next/versioned_docs/version-2.3.0/administration-geo.md
+++ b/site2/website-next/versioned_docs/version-2.3.0/administration-geo.md
@@ -129,23 +129,6 @@ $ bin/pulsar-admin namespaces set-clusters
my-tenant/my-namespace \
```
-#### Enable geo-replication at topic level
-
-You can set geo-replication at topic level using the command `pulsar-admin
topics set-replication-clusters`. For the latest and complete information about
`Pulsar admin`, including commands, flags, descriptions, and more information,
see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
-
-```shell
-
-$ bin/pulsar-admin topics set-replication-clusters --clusters
us-west,us-east,us-cent my-tenant/my-namespace/my-topic
-
-```
-
-:::tip
-
-- 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.
-
-:::
-
### Use topics with geo-replication
#### Selective replication
diff --git
a/site2/website-next/versioned_docs/version-2.3.1/administration-geo.md
b/site2/website-next/versioned_docs/version-2.3.1/administration-geo.md
index c4463fb1205..78f72e1832e 100644
--- a/site2/website-next/versioned_docs/version-2.3.1/administration-geo.md
+++ b/site2/website-next/versioned_docs/version-2.3.1/administration-geo.md
@@ -129,23 +129,6 @@ $ bin/pulsar-admin namespaces set-clusters
my-tenant/my-namespace \
```
-#### Enable geo-replication at topic level
-
-You can set geo-replication at topic level using the command `pulsar-admin
topics set-replication-clusters`. For the latest and complete information about
`Pulsar admin`, including commands, flags, descriptions, and more information,
see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
-
-```shell
-
-$ bin/pulsar-admin topics set-replication-clusters --clusters
us-west,us-east,us-cent my-tenant/my-namespace/my-topic
-
-```
-
-:::tip
-
-- 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.
-
-:::
-
### Use topics with geo-replication
#### Selective replication
diff --git
a/site2/website-next/versioned_docs/version-2.7.0/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.7.0/tiered-storage-overview.md
index 846a5a5387b..7c6528ce2b3 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/tiered-storage-overview.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/tiered-storage-overview.md
@@ -13,8 +13,9 @@ Pulsar's **Tiered Storage** feature allows older backlog data
to be moved from B
:::tip
- For more information about how to use the AWS S3 offloader with Pulsar, see
[here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
:::
diff --git
a/site2/website-next/versioned_docs/version-2.7.2/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.7.2/tiered-storage-overview.md
index 846a5a5387b..7c6528ce2b3 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/tiered-storage-overview.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/tiered-storage-overview.md
@@ -13,8 +13,9 @@ Pulsar's **Tiered Storage** feature allows older backlog data
to be moved from B
:::tip
- For more information about how to use the AWS S3 offloader with Pulsar, see
[here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
:::
diff --git
a/site2/website-next/versioned_docs/version-2.7.3/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.7.3/tiered-storage-overview.md
index 846a5a5387b..7c6528ce2b3 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/tiered-storage-overview.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/tiered-storage-overview.md
@@ -13,8 +13,9 @@ Pulsar's **Tiered Storage** feature allows older backlog data
to be moved from B
:::tip
- For more information about how to use the AWS S3 offloader with Pulsar, see
[here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
:::
diff --git
a/site2/website-next/versioned_docs/version-2.7.4/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.7.4/tiered-storage-overview.md
index 846a5a5387b..7c6528ce2b3 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/tiered-storage-overview.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/tiered-storage-overview.md
@@ -13,8 +13,9 @@ Pulsar's **Tiered Storage** feature allows older backlog data
to be moved from B
:::tip
- For more information about how to use the AWS S3 offloader with Pulsar, see
[here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
:::
diff --git
a/site2/website-next/versioned_docs/version-2.8.0/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.8.0/tiered-storage-overview.md
index 846a5a5387b..7c6528ce2b3 100644
--- a/site2/website-next/versioned_docs/version-2.8.0/tiered-storage-overview.md
+++ b/site2/website-next/versioned_docs/version-2.8.0/tiered-storage-overview.md
@@ -13,8 +13,9 @@ Pulsar's **Tiered Storage** feature allows older backlog data
to be moved from B
:::tip
- For more information about how to use the AWS S3 offloader with Pulsar, see
[here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
:::
diff --git
a/site2/website-next/versioned_docs/version-2.8.1/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.8.1/tiered-storage-overview.md
index 846a5a5387b..7c6528ce2b3 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/tiered-storage-overview.md
+++ b/site2/website-next/versioned_docs/version-2.8.1/tiered-storage-overview.md
@@ -13,8 +13,9 @@ Pulsar's **Tiered Storage** feature allows older backlog data
to be moved from B
:::tip
- For more information about how to use the AWS S3 offloader with Pulsar, see
[here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
:::
diff --git
a/site2/website-next/versioned_docs/version-2.8.2/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.8.2/tiered-storage-overview.md
index 9d8cef8e4b5..7c6528ce2b3 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/tiered-storage-overview.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/tiered-storage-overview.md
@@ -11,12 +11,13 @@ Pulsar's **Tiered Storage** feature allows older backlog
data to be moved from B
With jclouds, it is easy to add support for more [cloud storage
providers](https://jclouds.apache.org/reference/providers/#blobstore-providers)
in the future.
- :::tip
+ :::tip
- For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
- :::
+ :::
* Tiered storage uses [Apache Hadoop](http://hadoop.apache.org/) to support
filesystems for long term storage.
diff --git
a/site2/website-next/versioned_docs/version-2.8.3/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.8.3/tiered-storage-overview.md
index 9d8cef8e4b5..7c6528ce2b3 100644
--- a/site2/website-next/versioned_docs/version-2.8.3/tiered-storage-overview.md
+++ b/site2/website-next/versioned_docs/version-2.8.3/tiered-storage-overview.md
@@ -11,12 +11,13 @@ Pulsar's **Tiered Storage** feature allows older backlog
data to be moved from B
With jclouds, it is easy to add support for more [cloud storage
providers](https://jclouds.apache.org/reference/providers/#blobstore-providers)
in the future.
- :::tip
+ :::tip
- For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
- :::
+ :::
* Tiered storage uses [Apache Hadoop](http://hadoop.apache.org/) to support
filesystems for long term storage.
diff --git
a/site2/website-next/versioned_docs/version-2.9.0/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.9.0/tiered-storage-overview.md
index 9b7291b843e..7c6528ce2b3 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/tiered-storage-overview.md
+++ b/site2/website-next/versioned_docs/version-2.9.0/tiered-storage-overview.md
@@ -9,14 +9,15 @@ Pulsar's **Tiered Storage** feature allows older backlog data
to be moved from B
* Tiered storage uses [Apache jclouds](https://jclouds.apache.org) to support
[Amazon S3](https://aws.amazon.com/s3/) and [GCS (Google Cloud
Storage)](https://cloud.google.com/storage/) for long term storage.
- With jclouds, it is easy to add support for more [cloud storage
providers](https://jclouds.apache.org/reference/providers/#blobstore-providers)
in the future.
+ With jclouds, it is easy to add support for more [cloud storage
providers](https://jclouds.apache.org/reference/providers/#blobstore-providers)
in the future.
- :::tip
+ :::tip
- For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
- :::
+ :::
* Tiered storage uses [Apache Hadoop](http://hadoop.apache.org/) to support
filesystems for long term storage.
diff --git
a/site2/website-next/versioned_docs/version-2.9.1/administration-geo.md
b/site2/website-next/versioned_docs/version-2.9.1/administration-geo.md
index 57fba2b7232..65a5ca124f0 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/administration-geo.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/administration-geo.md
@@ -134,23 +134,6 @@ $ bin/pulsar-admin namespaces set-clusters
my-tenant/my-namespace \
```
-#### Enable geo-replication at topic level
-
-You can set geo-replication at topic level using the command `pulsar-admin
topics set-replication-clusters`. For the latest and complete information about
`Pulsar admin`, including commands, flags, descriptions, and more information,
see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
-
-```shell
-
-$ bin/pulsar-admin topics set-replication-clusters --clusters
us-west,us-east,us-cent my-tenant/my-namespace/my-topic
-
-```
-
-:::tip
-
-- 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.
-
-:::
-
### Use topics with geo-replication
Once you create a geo-replication namespace, any topics that producers or
consumers create within that namespace is replicated across clusters.
Typically, each application uses the `serviceUrl` for the local cluster.
diff --git
a/site2/website-next/versioned_docs/version-2.9.1/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.9.1/tiered-storage-overview.md
index 9b7291b843e..6c22c221493 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/tiered-storage-overview.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/tiered-storage-overview.md
@@ -11,12 +11,13 @@ Pulsar's **Tiered Storage** feature allows older backlog
data to be moved from B
With jclouds, it is easy to add support for more [cloud storage
providers](https://jclouds.apache.org/reference/providers/#blobstore-providers)
in the future.
- :::tip
+ :::tip
- For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
- :::
+ :::
* Tiered storage uses [Apache Hadoop](http://hadoop.apache.org/) to support
filesystems for long term storage.
diff --git
a/site2/website-next/versioned_docs/version-2.9.2/administration-geo.md
b/site2/website-next/versioned_docs/version-2.9.2/administration-geo.md
index 57fba2b7232..65a5ca124f0 100644
--- a/site2/website-next/versioned_docs/version-2.9.2/administration-geo.md
+++ b/site2/website-next/versioned_docs/version-2.9.2/administration-geo.md
@@ -134,23 +134,6 @@ $ bin/pulsar-admin namespaces set-clusters
my-tenant/my-namespace \
```
-#### Enable geo-replication at topic level
-
-You can set geo-replication at topic level using the command `pulsar-admin
topics set-replication-clusters`. For the latest and complete information about
`Pulsar admin`, including commands, flags, descriptions, and more information,
see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
-
-```shell
-
-$ bin/pulsar-admin topics set-replication-clusters --clusters
us-west,us-east,us-cent my-tenant/my-namespace/my-topic
-
-```
-
-:::tip
-
-- 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.
-
-:::
-
### Use topics with geo-replication
Once you create a geo-replication namespace, any topics that producers or
consumers create within that namespace is replicated across clusters.
Typically, each application uses the `serviceUrl` for the local cluster.
diff --git
a/site2/website-next/versioned_docs/version-2.9.2/tiered-storage-overview.md
b/site2/website-next/versioned_docs/version-2.9.2/tiered-storage-overview.md
index 9b7291b843e..7c6528ce2b3 100644
--- a/site2/website-next/versioned_docs/version-2.9.2/tiered-storage-overview.md
+++ b/site2/website-next/versioned_docs/version-2.9.2/tiered-storage-overview.md
@@ -9,14 +9,15 @@ Pulsar's **Tiered Storage** feature allows older backlog data
to be moved from B
* Tiered storage uses [Apache jclouds](https://jclouds.apache.org) to support
[Amazon S3](https://aws.amazon.com/s3/) and [GCS (Google Cloud
Storage)](https://cloud.google.com/storage/) for long term storage.
- With jclouds, it is easy to add support for more [cloud storage
providers](https://jclouds.apache.org/reference/providers/#blobstore-providers)
in the future.
+ With jclouds, it is easy to add support for more [cloud storage
providers](https://jclouds.apache.org/reference/providers/#blobstore-providers)
in the future.
- :::tip
+ :::tip
- For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
- For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
+ - For more information about how to use the AWS S3 offloader with Pulsar,
see [here](tiered-storage-aws).
+
+ - For more information about how to use the GCS offloader with Pulsar, see
[here](tiered-storage-gcs).
- :::
+ :::
* Tiered storage uses [Apache Hadoop](http://hadoop.apache.org/) to support
filesystems for long term storage.
