This is an automated email from the ASF dual-hosted git repository.
tison pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new b5f84cab9cf [improve][doc] Use metadataServiceUri in favor of
zkServers (#16159)
b5f84cab9cf is described below
commit b5f84cab9cf7a505a1d58ec420ef7daa364df2ee
Author: Dave Maughan <[email protected]>
AuthorDate: Thu Dec 29 02:21:56 2022 +0000
[improve][doc] Use metadataServiceUri in favor of zkServers (#16159)
---
conf/bookkeeper.conf | 8 ++++----
site2/docs/deploy-bare-metal.md | 6 +++---
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/conf/bookkeeper.conf b/conf/bookkeeper.conf
index 4083ba1d373..9661108acc0 100644
--- a/conf/bookkeeper.conf
+++ b/conf/bookkeeper.conf
@@ -642,10 +642,10 @@ diskCheckInterval=10000
## Metadata Service settings
#############################################################################
-# metadata service uri that bookkeeper is used for loading corresponding
metadata driver and resolving its metadata service location
+# Metadata service uri that bookkeeper uses for loading the corresponding
metadata driver and resolving its metadata service location
# Examples:
-# - metadataServiceUri=metadata-store:zk:my-zk-1:2181
-# - metadataServiceUri=metadata-store:etcd:http://my-etcd:2379
+# - metadataServiceUri=zk://my-zk-1:2181/ledgers
+# - metadataServiceUri=etcd:http://my-etcd:2379
metadataServiceUri=
# @Deprecated - `ledgerManagerFactoryClass` is deprecated in favor of using
`metadataServiceUri`
@@ -670,7 +670,7 @@ metadataServiceUri=
## ZooKeeper parameters
#############################################################################
-# @Deprecated - `zkLedgers` is deprecated in favor of using
`metadataServiceUri`
+# @Deprecated - `zkServers` is deprecated in favor of using
`metadataServiceUri`
# A list of one of more servers on which Zookeeper is running.
# The server list can be comma separated values, for example:
# zkServers=zk1:2181,zk2:2181,zk3:2181
diff --git a/site2/docs/deploy-bare-metal.md b/site2/docs/deploy-bare-metal.md
index 36dac7e0242..bacbe579413 100644
--- a/site2/docs/deploy-bare-metal.md
+++ b/site2/docs/deploy-bare-metal.md
@@ -295,13 +295,13 @@ You can obtain the metadata service URI of the existing
BookKeeper cluster by us
[BookKeeper](https://bookkeeper.apache.org) handles all persistent data
storage in Pulsar. You need to deploy a cluster of BookKeeper bookies to use
Pulsar. You can choose to run a **3-bookie BookKeeper cluster**.
-You can configure BookKeeper bookies using the
[`conf/bookkeeper.conf`](reference-configuration.md#bookkeeper) configuration
file. The most important step in configuring bookies for our purposes here is
ensuring that [`zkServers`](reference-configuration.md#bookkeeper-zkServers) is
set to the connection string for the ZooKeeper cluster. The following is an
example:
+You can configure BookKeeper bookies using the
[`conf/bookkeeper.conf`](reference-configuration.md#bookkeeper) configuration
file. The most important step in configuring bookies for our purposes here is
ensuring that `metadataServiceUri` is set to the URI for the ZooKeeper cluster.
The following is an example:
```properties
-zkServers=zk1.us-west.example.com:2181,zk2.us-west.example.com:2181,zk3.us-west.example.com:2181
+metadataServiceUri=zk://zk1.us-west.example.com:2181/ledgers
```
-Once you appropriately modify the `zkServers` parameter, you can make any
other configuration changes that you require. You can find a full listing of
the available BookKeeper configuration parameters
[here](reference-configuration.md#bookkeeper). However, consulting the
[BookKeeper
documentation](https://bookkeeper.apache.org/docs/next/reference/config/) for a
more in-depth guide might be a better choice.
+Once you appropriately modify the `metadataServiceUri` parameter, you can make
any other configuration changes that you require. You can find a full listing
of the available BookKeeper configuration parameters
[here](reference-configuration.md#bookkeeper). However, consulting the
[BookKeeper
documentation](https://bookkeeper.apache.org/docs/next/reference/config/) for a
more in-depth guide might be a better choice.
Once you apply the desired configuration in `conf/bookkeeper.conf`, you can
start up a bookie on each of your BookKeeper hosts. You can start up each
bookie either in the background, using
[nohup](https://en.wikipedia.org/wiki/Nohup), or in the foreground.
