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 9f5c0ee21f Docs sync done from apache/pulsar(#14260ac)
9f5c0ee21f is described below
commit 9f5c0ee21f252a40d6a23e4965e5b444168a2d97
Author: Pulsar Site Updater <[email protected]>
AuthorDate: Wed Apr 6 06:02:40 2022 +0000
Docs sync done from apache/pulsar(#14260ac)
---
site2/docs/deploy-bare-metal.md | 4 ++--
site2/website-next/docs/deploy-bare-metal.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.2/deploy-bare-metal.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.3/deploy-bare-metal.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.4/deploy-bare-metal.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.0/deploy-bare-metal.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.1/deploy-bare-metal.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.2/deploy-bare-metal.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.3/deploy-bare-metal.md | 4 ++--
site2/website-next/versioned_docs/version-2.9.0/deploy-bare-metal.md | 4 ++--
site2/website-next/versioned_docs/version-2.9.1/deploy-bare-metal.md | 4 ++--
site2/website-next/versioned_docs/version-2.9.2/deploy-bare-metal.md | 4 ++--
site2/website/versioned_docs/version-2.7.2/deploy-bare-metal.md | 4 ++--
site2/website/versioned_docs/version-2.7.3/deploy-bare-metal.md | 4 ++--
site2/website/versioned_docs/version-2.7.4/deploy-bare-metal.md | 4 ++--
site2/website/versioned_docs/version-2.8.0/deploy-bare-metal.md | 4 ++--
site2/website/versioned_docs/version-2.8.1/deploy-bare-metal.md | 4 ++--
site2/website/versioned_docs/version-2.8.2/deploy-bare-metal.md | 4 ++--
site2/website/versioned_docs/version-2.8.3/deploy-bare-metal.md | 4 ++--
site2/website/versioned_docs/version-2.9.0/deploy-bare-metal.md | 4 ++--
site2/website/versioned_docs/version-2.9.1/deploy-bare-metal.md | 4 ++--
site2/website/versioned_docs/version-2.9.2/deploy-bare-metal.md | 4 ++--
22 files changed, 44 insertions(+), 44 deletions(-)
diff --git a/site2/docs/deploy-bare-metal.md b/site2/docs/deploy-bare-metal.md
index 4a3592dbce..ff30a0d523 100644
--- a/site2/docs/deploy-bare-metal.md
+++ b/site2/docs/deploy-bare-metal.md
@@ -234,9 +234,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
$ bin/pulsar initialize-cluster-metadata \
diff --git a/site2/website-next/docs/deploy-bare-metal.md
b/site2/website-next/docs/deploy-bare-metal.md
index db0a84f847..e3c13aec41 100644
--- a/site2/website-next/docs/deploy-bare-metal.md
+++ b/site2/website-next/docs/deploy-bare-metal.md
@@ -262,9 +262,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
diff --git
a/site2/website-next/versioned_docs/version-2.7.2/deploy-bare-metal.md
b/site2/website-next/versioned_docs/version-2.7.2/deploy-bare-metal.md
index f814a11940..4ab21f499d 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/deploy-bare-metal.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/deploy-bare-metal.md
@@ -244,9 +244,9 @@ $ PULSAR_EXTRA_OPTS="-Dstats_server_port=8001"
bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
diff --git
a/site2/website-next/versioned_docs/version-2.7.3/deploy-bare-metal.md
b/site2/website-next/versioned_docs/version-2.7.3/deploy-bare-metal.md
index ca1c81bfba..fa398f0e63 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/deploy-bare-metal.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/deploy-bare-metal.md
@@ -236,9 +236,9 @@ $ PULSAR_EXTRA_OPTS="-Dstats_server_port=8001"
bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
diff --git
a/site2/website-next/versioned_docs/version-2.7.4/deploy-bare-metal.md
b/site2/website-next/versioned_docs/version-2.7.4/deploy-bare-metal.md
index ca1c81bfba..fa398f0e63 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/deploy-bare-metal.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/deploy-bare-metal.md
@@ -236,9 +236,9 @@ $ PULSAR_EXTRA_OPTS="-Dstats_server_port=8001"
bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
diff --git
a/site2/website-next/versioned_docs/version-2.8.0/deploy-bare-metal.md
b/site2/website-next/versioned_docs/version-2.8.0/deploy-bare-metal.md
index c97b035813..8effc857c1 100644
--- a/site2/website-next/versioned_docs/version-2.8.0/deploy-bare-metal.md
+++ b/site2/website-next/versioned_docs/version-2.8.0/deploy-bare-metal.md
@@ -236,9 +236,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
diff --git
a/site2/website-next/versioned_docs/version-2.8.1/deploy-bare-metal.md
b/site2/website-next/versioned_docs/version-2.8.1/deploy-bare-metal.md
index c97b035813..8effc857c1 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/deploy-bare-metal.md
+++ b/site2/website-next/versioned_docs/version-2.8.1/deploy-bare-metal.md
@@ -236,9 +236,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
diff --git
a/site2/website-next/versioned_docs/version-2.8.2/deploy-bare-metal.md
b/site2/website-next/versioned_docs/version-2.8.2/deploy-bare-metal.md
index a12dac4a60..3737b978ff 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/deploy-bare-metal.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/deploy-bare-metal.md
@@ -236,9 +236,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
diff --git
a/site2/website-next/versioned_docs/version-2.8.3/deploy-bare-metal.md
b/site2/website-next/versioned_docs/version-2.8.3/deploy-bare-metal.md
index c97b035813..8effc857c1 100644
--- a/site2/website-next/versioned_docs/version-2.8.3/deploy-bare-metal.md
+++ b/site2/website-next/versioned_docs/version-2.8.3/deploy-bare-metal.md
@@ -236,9 +236,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
diff --git
a/site2/website-next/versioned_docs/version-2.9.0/deploy-bare-metal.md
b/site2/website-next/versioned_docs/version-2.9.0/deploy-bare-metal.md
index 870c57cfef..755c753f38 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/deploy-bare-metal.md
+++ b/site2/website-next/versioned_docs/version-2.9.0/deploy-bare-metal.md
@@ -254,9 +254,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
diff --git
a/site2/website-next/versioned_docs/version-2.9.1/deploy-bare-metal.md
b/site2/website-next/versioned_docs/version-2.9.1/deploy-bare-metal.md
index 870c57cfef..755c753f38 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/deploy-bare-metal.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/deploy-bare-metal.md
@@ -254,9 +254,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
diff --git
a/site2/website-next/versioned_docs/version-2.9.2/deploy-bare-metal.md
b/site2/website-next/versioned_docs/version-2.9.2/deploy-bare-metal.md
index 35732ff105..f689723494 100644
--- a/site2/website-next/versioned_docs/version-2.9.2/deploy-bare-metal.md
+++ b/site2/website-next/versioned_docs/version-2.9.2/deploy-bare-metal.md
@@ -254,9 +254,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
diff --git a/site2/website/versioned_docs/version-2.7.2/deploy-bare-metal.md
b/site2/website/versioned_docs/version-2.7.2/deploy-bare-metal.md
index d2e0ebde7c..5a2844a02f 100644
--- a/site2/website/versioned_docs/version-2.7.2/deploy-bare-metal.md
+++ b/site2/website/versioned_docs/version-2.7.2/deploy-bare-metal.md
@@ -223,9 +223,9 @@ $ PULSAR_EXTRA_OPTS="-Dstats_server_port=8001"
bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
$ bin/pulsar initialize-cluster-metadata \
diff --git a/site2/website/versioned_docs/version-2.7.3/deploy-bare-metal.md
b/site2/website/versioned_docs/version-2.7.3/deploy-bare-metal.md
index bf17219f41..5b6cdc8834 100644
--- a/site2/website/versioned_docs/version-2.7.3/deploy-bare-metal.md
+++ b/site2/website/versioned_docs/version-2.7.3/deploy-bare-metal.md
@@ -217,9 +217,9 @@ $ PULSAR_EXTRA_OPTS="-Dstats_server_port=8001"
bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
$ bin/pulsar initialize-cluster-metadata \
diff --git a/site2/website/versioned_docs/version-2.7.4/deploy-bare-metal.md
b/site2/website/versioned_docs/version-2.7.4/deploy-bare-metal.md
index f5ae7d2ae9..a024157a20 100644
--- a/site2/website/versioned_docs/version-2.7.4/deploy-bare-metal.md
+++ b/site2/website/versioned_docs/version-2.7.4/deploy-bare-metal.md
@@ -217,9 +217,9 @@ $ PULSAR_EXTRA_OPTS="-Dstats_server_port=8001"
bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
$ bin/pulsar initialize-cluster-metadata \
diff --git a/site2/website/versioned_docs/version-2.8.0/deploy-bare-metal.md
b/site2/website/versioned_docs/version-2.8.0/deploy-bare-metal.md
index a4a1158538..fc5776966b 100644
--- a/site2/website/versioned_docs/version-2.8.0/deploy-bare-metal.md
+++ b/site2/website/versioned_docs/version-2.8.0/deploy-bare-metal.md
@@ -217,9 +217,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
$ bin/pulsar initialize-cluster-metadata \
diff --git a/site2/website/versioned_docs/version-2.8.1/deploy-bare-metal.md
b/site2/website/versioned_docs/version-2.8.1/deploy-bare-metal.md
index 118e3809b8..6dc15639dc 100644
--- a/site2/website/versioned_docs/version-2.8.1/deploy-bare-metal.md
+++ b/site2/website/versioned_docs/version-2.8.1/deploy-bare-metal.md
@@ -217,9 +217,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
$ bin/pulsar initialize-cluster-metadata \
diff --git a/site2/website/versioned_docs/version-2.8.2/deploy-bare-metal.md
b/site2/website/versioned_docs/version-2.8.2/deploy-bare-metal.md
index 1325b8472c..7ef6fe441f 100644
--- a/site2/website/versioned_docs/version-2.8.2/deploy-bare-metal.md
+++ b/site2/website/versioned_docs/version-2.8.2/deploy-bare-metal.md
@@ -217,9 +217,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
$ bin/pulsar initialize-cluster-metadata \
diff --git a/site2/website/versioned_docs/version-2.8.3/deploy-bare-metal.md
b/site2/website/versioned_docs/version-2.8.3/deploy-bare-metal.md
index 759e44f818..cb1dd0d3ec 100644
--- a/site2/website/versioned_docs/version-2.8.3/deploy-bare-metal.md
+++ b/site2/website/versioned_docs/version-2.8.3/deploy-bare-metal.md
@@ -217,9 +217,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
$ bin/pulsar initialize-cluster-metadata \
diff --git a/site2/website/versioned_docs/version-2.9.0/deploy-bare-metal.md
b/site2/website/versioned_docs/version-2.9.0/deploy-bare-metal.md
index 4dc2aeec8f..d28d0d9f69 100644
--- a/site2/website/versioned_docs/version-2.9.0/deploy-bare-metal.md
+++ b/site2/website/versioned_docs/version-2.9.0/deploy-bare-metal.md
@@ -230,9 +230,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
$ bin/pulsar initialize-cluster-metadata \
diff --git a/site2/website/versioned_docs/version-2.9.1/deploy-bare-metal.md
b/site2/website/versioned_docs/version-2.9.1/deploy-bare-metal.md
index c6389f4da0..8ef66ae7e4 100644
--- a/site2/website/versioned_docs/version-2.9.1/deploy-bare-metal.md
+++ b/site2/website/versioned_docs/version-2.9.1/deploy-bare-metal.md
@@ -230,9 +230,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
$ bin/pulsar initialize-cluster-metadata \
diff --git a/site2/website/versioned_docs/version-2.9.2/deploy-bare-metal.md
b/site2/website/versioned_docs/version-2.9.2/deploy-bare-metal.md
index b41bd240a4..cbfa12f958 100644
--- a/site2/website/versioned_docs/version-2.9.2/deploy-bare-metal.md
+++ b/site2/website/versioned_docs/version-2.9.2/deploy-bare-metal.md
@@ -230,9 +230,9 @@ $ bin/pulsar-daemon start zookeeper
## Initialize cluster metadata
-Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper for each cluster in your instance. You only need to write this data
**once**.
+Once you deploy ZooKeeper for your cluster, you need to write some metadata to
ZooKeeper. You only need to write this data **once**.
-You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your ZooKeeper cluster. The following is
an example:
+You can initialize this metadata using the
[`initialize-cluster-metadata`](reference-cli-tools.md#pulsar-initialize-cluster-metadata)
command of the [`pulsar`](reference-cli-tools.md#pulsar) CLI tool. This
command can be run on any machine in your Pulsar cluster, so the metadata can
be initialized from a ZooKeeper, broker, or bookie machine. The following is an
example:
```shell
$ bin/pulsar initialize-cluster-metadata \
