You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ur...@apache.org on 2022/03/12 06:02:40 UTC
[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#5f8db37)
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 e2344b9 Docs sync done from apache/pulsar(#5f8db37)
e2344b9 is described below
commit e2344b9305453aa5b5b21213205cb3541f177208
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Sat Mar 12 06:02:36 2022 +0000
Docs sync done from apache/pulsar(#5f8db37)
---
site2/docs/admin-api-clusters.md | 2 +-
site2/docs/client-libraries-go.md | 18 ++++++++++++++++-
site2/docs/concepts-architecture-overview.md | 2 +-
site2/docs/deploy-bare-metal-multi-cluster.md | 2 +-
site2/docs/deploy-bare-metal.md | 4 ++--
site2/docs/reference-cli-tools.md | 2 +-
site2/docs/reference-configuration.md | 5 ++++-
site2/docs/security-versioning-policy.md | 6 ------
site2/website-next/docs/admin-api-clusters.md | 2 +-
site2/website-next/docs/client-libraries-go.md | 23 +++++++++++++++++++++-
.../docs/concepts-architecture-overview.md | 2 +-
.../docs/deploy-bare-metal-multi-cluster.md | 2 +-
site2/website-next/docs/deploy-bare-metal.md | 4 ++--
site2/website-next/docs/reference-cli-tools.md | 2 +-
site2/website-next/docs/reference-configuration.md | 5 ++++-
.../docs/security-versioning-policy.md | 6 ------
.../version-2.2.0/admin-api-clusters.md | 2 +-
.../concepts-architecture-overview.md | 2 +-
.../version-2.2.0/reference-cli-tools.md | 2 +-
.../version-2.2.1/admin-api-clusters.md | 2 +-
.../concepts-architecture-overview.md | 2 +-
.../deploy-bare-metal-multi-cluster.md | 2 +-
.../version-2.2.1/reference-cli-tools.md | 2 +-
.../version-2.3.0/admin-api-clusters.md | 2 +-
.../concepts-architecture-overview.md | 2 +-
.../deploy-bare-metal-multi-cluster.md | 2 +-
.../version-2.3.1/admin-api-clusters.md | 2 +-
.../concepts-architecture-overview.md | 2 +-
.../version-2.3.2/admin-api-clusters.md | 2 +-
.../version-2.3.2/client-libraries-go.md | 23 +++++++++++++++++++++-
.../concepts-architecture-overview.md | 2 +-
.../deploy-bare-metal-multi-cluster.md | 2 +-
.../version-2.4.0/admin-api-clusters.md | 2 +-
.../concepts-architecture-overview.md | 2 +-
.../deploy-bare-metal-multi-cluster.md | 2 +-
.../version-2.4.1/admin-api-clusters.md | 2 +-
.../version-2.4.1/client-libraries-go.md | 23 +++++++++++++++++++++-
.../concepts-architecture-overview.md | 2 +-
.../deploy-bare-metal-multi-cluster.md | 2 +-
.../version-2.4.1/reference-cli-tools.md | 2 +-
.../version-2.4.2/admin-api-clusters.md | 2 +-
.../version-2.4.2/client-libraries-go.md | 23 +++++++++++++++++++++-
.../concepts-architecture-overview.md | 2 +-
.../deploy-bare-metal-multi-cluster.md | 2 +-
.../version-2.4.2/reference-cli-tools.md | 2 +-
.../version-2.5.0/admin-api-clusters.md | 2 +-
.../concepts-architecture-overview.md | 2 +-
.../version-2.5.1/admin-api-clusters.md | 2 +-
.../deploy-bare-metal-multi-cluster.md | 2 +-
.../version-2.5.2/admin-api-clusters.md | 2 +-
.../concepts-architecture-overview.md | 2 +-
.../deploy-bare-metal-multi-cluster.md | 2 +-
52 files changed, 158 insertions(+), 64 deletions(-)
diff --git a/site2/docs/admin-api-clusters.md b/site2/docs/admin-api-clusters.md
index dd09f58..50ac20a 100644
--- a/site2/docs/admin-api-clusters.md
+++ b/site2/docs/admin-api-clusters.md
@@ -64,7 +64,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/docs/client-libraries-go.md b/site2/docs/client-libraries-go.md
index 5534be0..be31491 100644
--- a/site2/docs/client-libraries-go.md
+++ b/site2/docs/client-libraries-go.md
@@ -16,7 +16,9 @@ You can use Pulsar [Go client](https://github.com/apache/pulsar-client-go) to cr
### Install go package
-You can install the `pulsar` library locally using `go get`.
+You can get the `pulsar` library by using `go get` or use it with `go module`.
+
+Download the library of Go client to local environment:
```bash
$ go get -u "github.com/apache/pulsar-client-go/pulsar"
@@ -28,6 +30,20 @@ Once installed locally, you can import it into your project:
import "github.com/apache/pulsar-client-go/pulsar"
```
+Use with go module:
+
+```bash
+$ mkdir test_dir && cd test_dir
+```
+Write a sample script in the `test_dir` directory (such as `test_example.go`) and write `package main` at the beginning of the file.
+
+```bash
+$ go mod init test_dir
+$ go mod tidy && go mod download
+$ go build test_example.go
+$ ./test_example
+```
+
## Connection URLs
To connect to Pulsar using client libraries, you need to specify a [Pulsar protocol](developing-binary-protocol.md) URL.
diff --git a/site2/docs/concepts-architecture-overview.md b/site2/docs/concepts-architecture-overview.md
index b33e75a..14f81b8 100644
--- a/site2/docs/concepts-architecture-overview.md
+++ b/site2/docs/concepts-architecture-overview.md
@@ -125,7 +125,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
$ cd /path/to/pulsar/directory
diff --git a/site2/docs/deploy-bare-metal-multi-cluster.md b/site2/docs/deploy-bare-metal-multi-cluster.md
index 71eb174..d8e9fd9 100644
--- a/site2/docs/deploy-bare-metal-multi-cluster.md
+++ b/site2/docs/deploy-bare-metal-multi-cluster.md
@@ -212,7 +212,7 @@ $ bin/pulsar initialize-cluster-metadata \
As you can see from the example above, you need to specify the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/docs/deploy-bare-metal.md b/site2/docs/deploy-bare-metal.md
index 4f73cbb..a8d4961 100644
--- a/site2/docs/deploy-bare-metal.md
+++ b/site2/docs/deploy-bare-metal.md
@@ -254,8 +254,8 @@ As you can see from the example above, you will need to specify the following:
Flag | Description
:----|:-----------
`--cluster` | A name for the cluster
-`--zookeeper` | A "local" ZooKeeper connection string for the cluster. This connection string only needs to include *one* machine in the ZooKeeper cluster.
-`--configuration-store` | The configuration store connection string for the entire instance. As with the `--zookeeper` flag, this connection string only needs to include *one* machine in the ZooKeeper cluster.
+`--metadata-store` | A "local" metadata store connection string for the cluster. This connection string only needs to include *one* machine in the ZooKeeper cluster.
+`--configuration-metadata-store` | The configuration metadata store connection string for the entire instance. As with the `--metadata-store` flag, this connection string only needs to include *one* machine in the ZooKeeper cluster.
`--web-service-url` | The web service URL for the cluster, plus a port. This URL should be a standard DNS name. The default port is 8080 (you had better not use a different port).
`--web-service-url-tls` | If you use [TLS](security-tls-transport.md), you also need to specify a TLS web service URL for the cluster. The default port is 8443 (you had better not use a different port).
`--broker-service-url` | A broker service URL enabling interaction with the brokers in the cluster. This URL should not use the same DNS name as the web service URL but should use the `pulsar` scheme instead. The default port is 6650 (you had better not use a different port).
diff --git a/site2/docs/reference-cli-tools.md b/site2/docs/reference-cli-tools.md
index b53ec81..995ce7e 100644
--- a/site2/docs/reference-cli-tools.md
+++ b/site2/docs/reference-cli-tools.md
@@ -190,7 +190,7 @@ Options
|Flag|Description|Default|
|---|---|---|
-|`-cms`, `--configuration-metadata-store`|Configuration meta store connection string||
+|`-cms`, `--configuration-metadata-store`|Configuration metadata store connection string||
|`-md` , `--metadata-store`|Metadata Store service url||
Example
diff --git a/site2/docs/reference-configuration.md b/site2/docs/reference-configuration.md
index 9e4dfc0..4c34007 100644
--- a/site2/docs/reference-configuration.md
+++ b/site2/docs/reference-configuration.md
@@ -716,6 +716,8 @@ The following parameters have been deprecated in the `conf/standalone.conf` file
|Name|Description|Default|
|---|---|---|
+|zookeeperServers| The quorum connection string for local metadata store. Use `metadataStoreUrl` instead. |N/A|
+|configurationStoreServers| Configuration store connection string (as a comma-separated list). Use `configurationMetadataStoreUrl` instead. |N/A|
|zooKeeperOperationTimeoutSeconds|ZooKeeper operation timeout in seconds. Use `metadataStoreOperationTimeoutSeconds` instead. |30|
|zooKeeperCacheExpirySeconds|ZooKeeper cache expiry time in seconds. Use `metadataStoreCacheExpirySeconds` instead. |300|
|zooKeeperSessionTimeoutMillis| The ZooKeeper session timeout, in milliseconds. Use `metadataStoreSessionTimeoutMillis` instead. |30000|
@@ -724,7 +726,7 @@ The following parameters have been deprecated in the `conf/standalone.conf` file
|Name|Description|Default|
|---|---|---|
-|configurationMetadataStoreUrl |||
+|configurationMetadataStoreUrl |Configuration store connection string. |N/A|
|metadataStoreSessionTimeoutMillis|Metadata store session timeout in milliseconds. |30000|
|metadataStoreCacheExpirySeconds|Metadata store cache expiry time in seconds|300|
|serviceUrl|||
@@ -754,6 +756,7 @@ The following parameters have been deprecated in the `conf/websocket.conf` file.
|---|---|---|
|zooKeeperSessionTimeoutMillis|The ZooKeeper session timeout in milliseconds. Use `metadataStoreSessionTimeoutMillis` instead. |30000|
|zooKeeperCacheExpirySeconds|ZooKeeper cache expiry time in seconds. Use `metadataStoreCacheExpirySeconds` instead.|300|
+|configurationStoreServers| Configuration Store connection string. Use `configurationMetadataStoreUrl` instead.|N/A|
## Pulsar proxy
diff --git a/site2/docs/security-versioning-policy.md b/site2/docs/security-versioning-policy.md
index 0b65f1b..7bfa1e0 100644
--- a/site2/docs/security-versioning-policy.md
+++ b/site2/docs/security-versioning-policy.md
@@ -4,12 +4,6 @@ title: Security Policy and Supported Versions
sidebar_label: Security Policy and Supported Versions
---
-## Reporting a Vulnerability
-
-The current process for reporting vulnerabilities is outlined here: https://www.apache.org/security/. When reporting a
-vulnerability to security@apache.org, you can copy your email to [private@pulsar.apache.org](mailto:private@pulsar.apache.org)
-to send your report to the Apache Pulsar Project Management Committee. This is a private mailing list.
-
## Using Pulsar's Security Features
You can find documentation on Pulsar's available security features and how to use them here:
diff --git a/site2/website-next/docs/admin-api-clusters.md b/site2/website-next/docs/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/docs/admin-api-clusters.md
+++ b/site2/website-next/docs/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/docs/client-libraries-go.md b/site2/website-next/docs/client-libraries-go.md
index 22df463..6a0922c 100644
--- a/site2/website-next/docs/client-libraries-go.md
+++ b/site2/website-next/docs/client-libraries-go.md
@@ -16,7 +16,9 @@ You can use Pulsar [Go client](https://github.com/apache/pulsar-client-go) to cr
### Install go package
-You can install the `pulsar` library locally using `go get`.
+You can get the `pulsar` library by using `go get` or use it with `go module`.
+
+Download the library of Go client to local environment:
```bash
@@ -32,6 +34,25 @@ import "github.com/apache/pulsar-client-go/pulsar"
```
+Use with go module:
+
+```bash
+
+$ mkdir test_dir && cd test_dir
+
+```
+
+Write a sample script in the `test_dir` directory (such as `test_example.go`) and write `package main` at the beginning of the file.
+
+```bash
+
+$ go mod init test_dir
+$ go mod tidy && go mod download
+$ go build test_example.go
+$ ./test_example
+
+```
+
## Connection URLs
To connect to Pulsar using client libraries, you need to specify a [Pulsar protocol](developing-binary-protocol) URL.
diff --git a/site2/website-next/docs/concepts-architecture-overview.md b/site2/website-next/docs/concepts-architecture-overview.md
index a2b024d..24493c2 100644
--- a/site2/website-next/docs/concepts-architecture-overview.md
+++ b/site2/website-next/docs/concepts-architecture-overview.md
@@ -127,7 +127,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
diff --git a/site2/website-next/docs/deploy-bare-metal-multi-cluster.md b/site2/website-next/docs/deploy-bare-metal-multi-cluster.md
index 875b75d..4374374 100644
--- a/site2/website-next/docs/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/docs/deploy-bare-metal-multi-cluster.md
@@ -238,7 +238,7 @@ $ bin/pulsar initialize-cluster-metadata \
As you can see from the example above, you need to specify the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/docs/deploy-bare-metal.md b/site2/website-next/docs/deploy-bare-metal.md
index f32701d..50661be 100644
--- a/site2/website-next/docs/deploy-bare-metal.md
+++ b/site2/website-next/docs/deploy-bare-metal.md
@@ -284,8 +284,8 @@ As you can see from the example above, you will need to specify the following:
Flag | Description
:----|:-----------
`--cluster` | A name for the cluster
-`--zookeeper` | A "local" ZooKeeper connection string for the cluster. This connection string only needs to include *one* machine in the ZooKeeper cluster.
-`--configuration-store` | The configuration store connection string for the entire instance. As with the `--zookeeper` flag, this connection string only needs to include *one* machine in the ZooKeeper cluster.
+`--metadata-store` | A "local" metadata store connection string for the cluster. This connection string only needs to include *one* machine in the ZooKeeper cluster.
+`--configuration-metadata-store` | The configuration metadata store connection string for the entire instance. As with the `--metadata-store` flag, this connection string only needs to include *one* machine in the ZooKeeper cluster.
`--web-service-url` | The web service URL for the cluster, plus a port. This URL should be a standard DNS name. The default port is 8080 (you had better not use a different port).
`--web-service-url-tls` | If you use [TLS](security-tls-transport), you also need to specify a TLS web service URL for the cluster. The default port is 8443 (you had better not use a different port).
`--broker-service-url` | A broker service URL enabling interaction with the brokers in the cluster. This URL should not use the same DNS name as the web service URL but should use the `pulsar` scheme instead. The default port is 6650 (you had better not use a different port).
diff --git a/site2/website-next/docs/reference-cli-tools.md b/site2/website-next/docs/reference-cli-tools.md
index 32b23e9..1c3d601 100644
--- a/site2/website-next/docs/reference-cli-tools.md
+++ b/site2/website-next/docs/reference-cli-tools.md
@@ -233,7 +233,7 @@ Options
|Flag|Description|Default|
|---|---|---|
-|`-cms`, `--configuration-metadata-store`|Configuration meta store connection string||
+|`-cms`, `--configuration-metadata-store`|Configuration metadata store connection string||
|`-md` , `--metadata-store`|Metadata Store service url||
Example
diff --git a/site2/website-next/docs/reference-configuration.md b/site2/website-next/docs/reference-configuration.md
index d469c11..4698ffc 100644
--- a/site2/website-next/docs/reference-configuration.md
+++ b/site2/website-next/docs/reference-configuration.md
@@ -712,6 +712,8 @@ The following parameters have been deprecated in the `conf/standalone.conf` file
|Name|Description|Default|
|---|---|---|
+|zookeeperServers| The quorum connection string for local metadata store. Use `metadataStoreUrl` instead. |N/A|
+|configurationStoreServers| Configuration store connection string (as a comma-separated list). Use `configurationMetadataStoreUrl` instead. |N/A|
|zooKeeperOperationTimeoutSeconds|ZooKeeper operation timeout in seconds. Use `metadataStoreOperationTimeoutSeconds` instead. |30|
|zooKeeperCacheExpirySeconds|ZooKeeper cache expiry time in seconds. Use `metadataStoreCacheExpirySeconds` instead. |300|
|zooKeeperSessionTimeoutMillis| The ZooKeeper session timeout, in milliseconds. Use `metadataStoreSessionTimeoutMillis` instead. |30000|
@@ -720,7 +722,7 @@ The following parameters have been deprecated in the `conf/standalone.conf` file
|Name|Description|Default|
|---|---|---|
-|configurationMetadataStoreUrl |||
+|configurationMetadataStoreUrl |Configuration store connection string. |N/A|
|metadataStoreSessionTimeoutMillis|Metadata store session timeout in milliseconds. |30000|
|metadataStoreCacheExpirySeconds|Metadata store cache expiry time in seconds|300|
|serviceUrl|||
@@ -750,6 +752,7 @@ The following parameters have been deprecated in the `conf/websocket.conf` file.
|---|---|---|
|zooKeeperSessionTimeoutMillis|The ZooKeeper session timeout in milliseconds. Use `metadataStoreSessionTimeoutMillis` instead. |30000|
|zooKeeperCacheExpirySeconds|ZooKeeper cache expiry time in seconds. Use `metadataStoreCacheExpirySeconds` instead.|300|
+|configurationStoreServers| Configuration Store connection string. Use `configurationMetadataStoreUrl` instead.|N/A|
## Pulsar proxy
diff --git a/site2/website-next/docs/security-versioning-policy.md b/site2/website-next/docs/security-versioning-policy.md
index 88a14e0..532d897 100644
--- a/site2/website-next/docs/security-versioning-policy.md
+++ b/site2/website-next/docs/security-versioning-policy.md
@@ -4,12 +4,6 @@ title: Security Policy and Supported Versions
sidebar_label: "Security Policy and Supported Versions"
---
-## Reporting a Vulnerability
-
-The current process for reporting vulnerabilities is outlined here: https://www.apache.org/security/. When reporting a
-vulnerability to security@apache.org, you can copy your email to [private@pulsar.apache.org](mailto:private@pulsar.apache.org)
-to send your report to the Apache Pulsar Project Management Committee. This is a private mailing list.
-
## Using Pulsar's Security Features
You can find documentation on Pulsar's available security features and how to use them here:
diff --git a/site2/website-next/versioned_docs/version-2.2.0/admin-api-clusters.md b/site2/website-next/versioned_docs/version-2.2.0/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/versioned_docs/version-2.2.0/admin-api-clusters.md
+++ b/site2/website-next/versioned_docs/version-2.2.0/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.2.0/concepts-architecture-overview.md b/site2/website-next/versioned_docs/version-2.2.0/concepts-architecture-overview.md
index a2b024d..24493c2 100644
--- a/site2/website-next/versioned_docs/version-2.2.0/concepts-architecture-overview.md
+++ b/site2/website-next/versioned_docs/version-2.2.0/concepts-architecture-overview.md
@@ -127,7 +127,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
diff --git a/site2/website-next/versioned_docs/version-2.2.0/reference-cli-tools.md b/site2/website-next/versioned_docs/version-2.2.0/reference-cli-tools.md
index 32b23e9..1c3d601 100644
--- a/site2/website-next/versioned_docs/version-2.2.0/reference-cli-tools.md
+++ b/site2/website-next/versioned_docs/version-2.2.0/reference-cli-tools.md
@@ -233,7 +233,7 @@ Options
|Flag|Description|Default|
|---|---|---|
-|`-cms`, `--configuration-metadata-store`|Configuration meta store connection string||
+|`-cms`, `--configuration-metadata-store`|Configuration metadata store connection string||
|`-md` , `--metadata-store`|Metadata Store service url||
Example
diff --git a/site2/website-next/versioned_docs/version-2.2.1/admin-api-clusters.md b/site2/website-next/versioned_docs/version-2.2.1/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/versioned_docs/version-2.2.1/admin-api-clusters.md
+++ b/site2/website-next/versioned_docs/version-2.2.1/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.2.1/concepts-architecture-overview.md b/site2/website-next/versioned_docs/version-2.2.1/concepts-architecture-overview.md
index a2b024d..24493c2 100644
--- a/site2/website-next/versioned_docs/version-2.2.1/concepts-architecture-overview.md
+++ b/site2/website-next/versioned_docs/version-2.2.1/concepts-architecture-overview.md
@@ -127,7 +127,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
diff --git a/site2/website-next/versioned_docs/version-2.2.1/deploy-bare-metal-multi-cluster.md b/site2/website-next/versioned_docs/version-2.2.1/deploy-bare-metal-multi-cluster.md
index 875b75d..4374374 100644
--- a/site2/website-next/versioned_docs/version-2.2.1/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/versioned_docs/version-2.2.1/deploy-bare-metal-multi-cluster.md
@@ -238,7 +238,7 @@ $ bin/pulsar initialize-cluster-metadata \
As you can see from the example above, you need to specify the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.2.1/reference-cli-tools.md b/site2/website-next/versioned_docs/version-2.2.1/reference-cli-tools.md
index 32b23e9..1c3d601 100644
--- a/site2/website-next/versioned_docs/version-2.2.1/reference-cli-tools.md
+++ b/site2/website-next/versioned_docs/version-2.2.1/reference-cli-tools.md
@@ -233,7 +233,7 @@ Options
|Flag|Description|Default|
|---|---|---|
-|`-cms`, `--configuration-metadata-store`|Configuration meta store connection string||
+|`-cms`, `--configuration-metadata-store`|Configuration metadata store connection string||
|`-md` , `--metadata-store`|Metadata Store service url||
Example
diff --git a/site2/website-next/versioned_docs/version-2.3.0/admin-api-clusters.md b/site2/website-next/versioned_docs/version-2.3.0/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/versioned_docs/version-2.3.0/admin-api-clusters.md
+++ b/site2/website-next/versioned_docs/version-2.3.0/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.3.0/concepts-architecture-overview.md b/site2/website-next/versioned_docs/version-2.3.0/concepts-architecture-overview.md
index a2b024d..24493c2 100644
--- a/site2/website-next/versioned_docs/version-2.3.0/concepts-architecture-overview.md
+++ b/site2/website-next/versioned_docs/version-2.3.0/concepts-architecture-overview.md
@@ -127,7 +127,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
diff --git a/site2/website-next/versioned_docs/version-2.3.0/deploy-bare-metal-multi-cluster.md b/site2/website-next/versioned_docs/version-2.3.0/deploy-bare-metal-multi-cluster.md
index 875b75d..4374374 100644
--- a/site2/website-next/versioned_docs/version-2.3.0/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/versioned_docs/version-2.3.0/deploy-bare-metal-multi-cluster.md
@@ -238,7 +238,7 @@ $ bin/pulsar initialize-cluster-metadata \
As you can see from the example above, you need to specify the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.3.1/admin-api-clusters.md b/site2/website-next/versioned_docs/version-2.3.1/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/versioned_docs/version-2.3.1/admin-api-clusters.md
+++ b/site2/website-next/versioned_docs/version-2.3.1/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.3.1/concepts-architecture-overview.md b/site2/website-next/versioned_docs/version-2.3.1/concepts-architecture-overview.md
index a2b024d..24493c2 100644
--- a/site2/website-next/versioned_docs/version-2.3.1/concepts-architecture-overview.md
+++ b/site2/website-next/versioned_docs/version-2.3.1/concepts-architecture-overview.md
@@ -127,7 +127,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
diff --git a/site2/website-next/versioned_docs/version-2.3.2/admin-api-clusters.md b/site2/website-next/versioned_docs/version-2.3.2/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/admin-api-clusters.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.3.2/client-libraries-go.md b/site2/website-next/versioned_docs/version-2.3.2/client-libraries-go.md
index 22df463..6a0922c 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/client-libraries-go.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/client-libraries-go.md
@@ -16,7 +16,9 @@ You can use Pulsar [Go client](https://github.com/apache/pulsar-client-go) to cr
### Install go package
-You can install the `pulsar` library locally using `go get`.
+You can get the `pulsar` library by using `go get` or use it with `go module`.
+
+Download the library of Go client to local environment:
```bash
@@ -32,6 +34,25 @@ import "github.com/apache/pulsar-client-go/pulsar"
```
+Use with go module:
+
+```bash
+
+$ mkdir test_dir && cd test_dir
+
+```
+
+Write a sample script in the `test_dir` directory (such as `test_example.go`) and write `package main` at the beginning of the file.
+
+```bash
+
+$ go mod init test_dir
+$ go mod tidy && go mod download
+$ go build test_example.go
+$ ./test_example
+
+```
+
## Connection URLs
To connect to Pulsar using client libraries, you need to specify a [Pulsar protocol](developing-binary-protocol) URL.
diff --git a/site2/website-next/versioned_docs/version-2.3.2/concepts-architecture-overview.md b/site2/website-next/versioned_docs/version-2.3.2/concepts-architecture-overview.md
index a2b024d..24493c2 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/concepts-architecture-overview.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/concepts-architecture-overview.md
@@ -127,7 +127,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
diff --git a/site2/website-next/versioned_docs/version-2.3.2/deploy-bare-metal-multi-cluster.md b/site2/website-next/versioned_docs/version-2.3.2/deploy-bare-metal-multi-cluster.md
index 875b75d..4374374 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/deploy-bare-metal-multi-cluster.md
@@ -238,7 +238,7 @@ $ bin/pulsar initialize-cluster-metadata \
As you can see from the example above, you need to specify the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.4.0/admin-api-clusters.md b/site2/website-next/versioned_docs/version-2.4.0/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/versioned_docs/version-2.4.0/admin-api-clusters.md
+++ b/site2/website-next/versioned_docs/version-2.4.0/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.4.0/concepts-architecture-overview.md b/site2/website-next/versioned_docs/version-2.4.0/concepts-architecture-overview.md
index a2b024d..24493c2 100644
--- a/site2/website-next/versioned_docs/version-2.4.0/concepts-architecture-overview.md
+++ b/site2/website-next/versioned_docs/version-2.4.0/concepts-architecture-overview.md
@@ -127,7 +127,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
diff --git a/site2/website-next/versioned_docs/version-2.4.0/deploy-bare-metal-multi-cluster.md b/site2/website-next/versioned_docs/version-2.4.0/deploy-bare-metal-multi-cluster.md
index 875b75d..4374374 100644
--- a/site2/website-next/versioned_docs/version-2.4.0/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/versioned_docs/version-2.4.0/deploy-bare-metal-multi-cluster.md
@@ -238,7 +238,7 @@ $ bin/pulsar initialize-cluster-metadata \
As you can see from the example above, you need to specify the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.4.1/admin-api-clusters.md b/site2/website-next/versioned_docs/version-2.4.1/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/admin-api-clusters.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.4.1/client-libraries-go.md b/site2/website-next/versioned_docs/version-2.4.1/client-libraries-go.md
index 22df463..6a0922c 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/client-libraries-go.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/client-libraries-go.md
@@ -16,7 +16,9 @@ You can use Pulsar [Go client](https://github.com/apache/pulsar-client-go) to cr
### Install go package
-You can install the `pulsar` library locally using `go get`.
+You can get the `pulsar` library by using `go get` or use it with `go module`.
+
+Download the library of Go client to local environment:
```bash
@@ -32,6 +34,25 @@ import "github.com/apache/pulsar-client-go/pulsar"
```
+Use with go module:
+
+```bash
+
+$ mkdir test_dir && cd test_dir
+
+```
+
+Write a sample script in the `test_dir` directory (such as `test_example.go`) and write `package main` at the beginning of the file.
+
+```bash
+
+$ go mod init test_dir
+$ go mod tidy && go mod download
+$ go build test_example.go
+$ ./test_example
+
+```
+
## Connection URLs
To connect to Pulsar using client libraries, you need to specify a [Pulsar protocol](developing-binary-protocol) URL.
diff --git a/site2/website-next/versioned_docs/version-2.4.1/concepts-architecture-overview.md b/site2/website-next/versioned_docs/version-2.4.1/concepts-architecture-overview.md
index a2b024d..24493c2 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/concepts-architecture-overview.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/concepts-architecture-overview.md
@@ -127,7 +127,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
diff --git a/site2/website-next/versioned_docs/version-2.4.1/deploy-bare-metal-multi-cluster.md b/site2/website-next/versioned_docs/version-2.4.1/deploy-bare-metal-multi-cluster.md
index 875b75d..4374374 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/deploy-bare-metal-multi-cluster.md
@@ -238,7 +238,7 @@ $ bin/pulsar initialize-cluster-metadata \
As you can see from the example above, you need to specify the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.4.1/reference-cli-tools.md b/site2/website-next/versioned_docs/version-2.4.1/reference-cli-tools.md
index 32b23e9..1c3d601 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/reference-cli-tools.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/reference-cli-tools.md
@@ -233,7 +233,7 @@ Options
|Flag|Description|Default|
|---|---|---|
-|`-cms`, `--configuration-metadata-store`|Configuration meta store connection string||
+|`-cms`, `--configuration-metadata-store`|Configuration metadata store connection string||
|`-md` , `--metadata-store`|Metadata Store service url||
Example
diff --git a/site2/website-next/versioned_docs/version-2.4.2/admin-api-clusters.md b/site2/website-next/versioned_docs/version-2.4.2/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/versioned_docs/version-2.4.2/admin-api-clusters.md
+++ b/site2/website-next/versioned_docs/version-2.4.2/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.4.2/client-libraries-go.md b/site2/website-next/versioned_docs/version-2.4.2/client-libraries-go.md
index 22df463..6a0922c 100644
--- a/site2/website-next/versioned_docs/version-2.4.2/client-libraries-go.md
+++ b/site2/website-next/versioned_docs/version-2.4.2/client-libraries-go.md
@@ -16,7 +16,9 @@ You can use Pulsar [Go client](https://github.com/apache/pulsar-client-go) to cr
### Install go package
-You can install the `pulsar` library locally using `go get`.
+You can get the `pulsar` library by using `go get` or use it with `go module`.
+
+Download the library of Go client to local environment:
```bash
@@ -32,6 +34,25 @@ import "github.com/apache/pulsar-client-go/pulsar"
```
+Use with go module:
+
+```bash
+
+$ mkdir test_dir && cd test_dir
+
+```
+
+Write a sample script in the `test_dir` directory (such as `test_example.go`) and write `package main` at the beginning of the file.
+
+```bash
+
+$ go mod init test_dir
+$ go mod tidy && go mod download
+$ go build test_example.go
+$ ./test_example
+
+```
+
## Connection URLs
To connect to Pulsar using client libraries, you need to specify a [Pulsar protocol](developing-binary-protocol) URL.
diff --git a/site2/website-next/versioned_docs/version-2.4.2/concepts-architecture-overview.md b/site2/website-next/versioned_docs/version-2.4.2/concepts-architecture-overview.md
index a2b024d..24493c2 100644
--- a/site2/website-next/versioned_docs/version-2.4.2/concepts-architecture-overview.md
+++ b/site2/website-next/versioned_docs/version-2.4.2/concepts-architecture-overview.md
@@ -127,7 +127,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
diff --git a/site2/website-next/versioned_docs/version-2.4.2/deploy-bare-metal-multi-cluster.md b/site2/website-next/versioned_docs/version-2.4.2/deploy-bare-metal-multi-cluster.md
index 875b75d..4374374 100644
--- a/site2/website-next/versioned_docs/version-2.4.2/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/versioned_docs/version-2.4.2/deploy-bare-metal-multi-cluster.md
@@ -238,7 +238,7 @@ $ bin/pulsar initialize-cluster-metadata \
As you can see from the example above, you need to specify the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.4.2/reference-cli-tools.md b/site2/website-next/versioned_docs/version-2.4.2/reference-cli-tools.md
index 32b23e9..1c3d601 100644
--- a/site2/website-next/versioned_docs/version-2.4.2/reference-cli-tools.md
+++ b/site2/website-next/versioned_docs/version-2.4.2/reference-cli-tools.md
@@ -233,7 +233,7 @@ Options
|Flag|Description|Default|
|---|---|---|
-|`-cms`, `--configuration-metadata-store`|Configuration meta store connection string||
+|`-cms`, `--configuration-metadata-store`|Configuration metadata store connection string||
|`-md` , `--metadata-store`|Metadata Store service url||
Example
diff --git a/site2/website-next/versioned_docs/version-2.5.0/admin-api-clusters.md b/site2/website-next/versioned_docs/version-2.5.0/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/versioned_docs/version-2.5.0/admin-api-clusters.md
+++ b/site2/website-next/versioned_docs/version-2.5.0/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.5.0/concepts-architecture-overview.md b/site2/website-next/versioned_docs/version-2.5.0/concepts-architecture-overview.md
index a2b024d..24493c2 100644
--- a/site2/website-next/versioned_docs/version-2.5.0/concepts-architecture-overview.md
+++ b/site2/website-next/versioned_docs/version-2.5.0/concepts-architecture-overview.md
@@ -127,7 +127,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
diff --git a/site2/website-next/versioned_docs/version-2.5.1/admin-api-clusters.md b/site2/website-next/versioned_docs/version-2.5.1/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/admin-api-clusters.md
+++ b/site2/website-next/versioned_docs/version-2.5.1/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.5.1/deploy-bare-metal-multi-cluster.md b/site2/website-next/versioned_docs/version-2.5.1/deploy-bare-metal-multi-cluster.md
index 875b75d..4374374 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/versioned_docs/version-2.5.1/deploy-bare-metal-multi-cluster.md
@@ -238,7 +238,7 @@ $ bin/pulsar initialize-cluster-metadata \
As you can see from the example above, you need to specify the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.5.2/admin-api-clusters.md b/site2/website-next/versioned_docs/version-2.5.2/admin-api-clusters.md
index 3c2f661..418626f 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/admin-api-clusters.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/admin-api-clusters.md
@@ -83,7 +83,7 @@ admin.clusters().createCluster(clusterName, clusterData);
When provision a new cluster, you need to initialize that cluster's [metadata](concepts-architecture-overview.md#metadata-store). When initializing cluster metadata, you need to specify all of the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster
diff --git a/site2/website-next/versioned_docs/version-2.5.2/concepts-architecture-overview.md b/site2/website-next/versioned_docs/version-2.5.2/concepts-architecture-overview.md
index a2b024d..24493c2 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/concepts-architecture-overview.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/concepts-architecture-overview.md
@@ -127,7 +127,7 @@ The **Pulsar proxy** provides a solution to this problem by acting as a single g
> For the sake of performance and fault tolerance, you can run as many instances of the Pulsar proxy as you'd like.
-Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide ZooKeeper connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
+Architecturally, the Pulsar proxy gets all the information it requires from ZooKeeper. When starting the proxy on a machine, you only need to provide metadata store connection strings for the cluster-specific and instance-wide configuration store clusters. Here's an example:
```bash
diff --git a/site2/website-next/versioned_docs/version-2.5.2/deploy-bare-metal-multi-cluster.md b/site2/website-next/versioned_docs/version-2.5.2/deploy-bare-metal-multi-cluster.md
index 875b75d..4374374 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/deploy-bare-metal-multi-cluster.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/deploy-bare-metal-multi-cluster.md
@@ -238,7 +238,7 @@ $ bin/pulsar initialize-cluster-metadata \
As you can see from the example above, you need to specify the following:
* The name of the cluster
-* The local ZooKeeper connection string for the cluster
+* The local metadata store connection string for the cluster
* The configuration store connection string for the entire instance
* The web service URL for the cluster
* A broker service URL enabling interaction with the [brokers](reference-terminology.md#broker) in the cluster