部署Pulsar集群包括以下步骤(按顺序)：

• Deploy a ZooKeeper cluster (optional)
• Initialize
• Deploy a BookKeeper cluster
• Deploy one or more Pulsar

If you already have an existing zookeeper cluster and want to reuse it, you do not need to prepare the machines for running ZooKeeper.

To run Pulsar on bare metal, the following configuration is recommended:

• 至少 6 台 Linux 机器或虚拟机
  • 3 for running ZooKeeper
  • 3 for running a Pulsar broker, and a bookie
• 包含 Pulsar 所有 broker 主机的 DNS（域名解析服务器）

If you do not have enough machines, or to try out Pulsar in cluster mode (and expand the cluster later), you can deploy a full Pulsar configuration on one node, where Zookeeper, the bookie and broker are run on the same machine.

If you do not have a DNS server, you can use the multi-host format in the service URL instead.

Each machine in your cluster needs to have or a more recent version of Java installed.

The following is a diagram showing the basic setup:

In this diagram, connecting clients need to be able to communicate with the Pulsar cluster using a single URL. In this case, pulsar-cluster.acme.com abstracts over all of the message-handling brokers. Pulsar消息brokers与BookKeeper bookies一起运行；反过来，brokers 和 bookies 都依赖 ZooKeeper。

When you deploy a Pulsar cluster, keep in mind the following basic better choices when you do the capacity planning.

ZooKeeper

For machines running ZooKeeper, is is recommended to use less powerful machines or VMs. Pulsar uses ZooKeeper only for periodic coordination-related and configuration-related tasks, not for basic operations. If you run Pulsar on (AWS), for example, a t2.small instance might likely suffice.

Bookies and Brokers

For machines running a bookie and a Pulsar broker, more powerful machines are required. 例如，对于AWS部署，i3.4xlarge实例可能是合适的。 On those machines you can use the following:

• 高性能的CPU和10Gbps （适用于Pulsar brokers）
• 小型快速固态硬盘（SSD）或（HDD），带有RAID控制器和电池供电的写缓存（适用于BookKeeper bookies）

Install the Pulsar binary package

You need to install the Pulsar binary package on each machine in the cluster, including machines running ZooKeeper and .

To get started deploying a Pulsar cluster on bare metal, you need to download a binary tarball release in one of the following ways:

• By clicking on the link below directly, which automatically triggers a download:
  • Pulsar 2.6.1 binary release
• 从Pulsar的 下载
• 从Pulsar在 GitHub 的
• 使用 wget 命令下载:

Once you download the tarball, untar it and cd into the resulting directory:

$ tar xvzf apache-pulsar-2.6.1-bin.tar.gz
$ cd apache-pulsar-2.6.1

The extracted directory contains the following subdirectories:

Install Builtin Connectors (optional)

Since Pulsar release 2.1.0-incubating, Pulsar provides a separate binary distribution, containing all the builtin connectors. If you want to enable those builtin connectors, you can follow the instructions as below; otherwise you can skip this section for now.

To get started using builtin connectors, you need to download the connectors tarball release on every broker node in one of the following ways:

• 通过单击下面的链接并从 Apache 镜像下载该版本:

• Pulsar 下载页面

• Pulsar

• 使用 wget：

  $ wget https://archive.apache.org/dist/pulsar/pulsar-2.6.1/connectors/{connector}-2.6.1.nar

Once you download the .nar file, copy the file to directory connectors in the pulsar directory. For example, if you download the connector file pulsar-io-aerospike-2.6.1.nar:

$ mkdir connectors
$ mv pulsar-io-aerospike-2.6.1.nar connectors
$ ls connectors
pulsar-io-aerospike-2.6.1.nar

To get started using tiered storage offloaders, you need to download the offloaders tarball release on every broker node in one of the following ways:

• 通过单击下面的链接并从 Apache 镜像下载该版本:

• Pulsar 下载页面

• Pulsar

• 使用 wget：

  $ wget https://archive.apache.org/dist/pulsar/pulsar-2.6.1/apache-pulsar-offloaders-2.6.1-bin.tar.gz

Once you download the tarball, in the pulsar directory, untar the offloaders package and copy the offloaders as offloaders in the pulsar directory:

$ tar xvfz apache-pulsar-offloaders-2.6.1-bin.tar.gz
// you can find a directory named `apache-pulsar-offloaders-2.6.1` in the pulsar directory
// then copy the offloaders
$ mv apache-pulsar-offloaders-2.6.1/offloaders offloaders
$ ls offloaders
tiered-storage-jcloud-2.6.1.nar

For more details of how to configure tiered storage feature, you can refer to the

Deploy a ZooKeeper cluster

If you already have an exsiting zookeeper cluster and want to use it, you can skip this section.

manages a variety of essential coordination- and configuration-related tasks for Pulsar. To deploy a Pulsar cluster, you need to deploy ZooKeeper first (before all other components). A 3-node ZooKeeper cluster is the recommended configuration. Pulsar does not make heavy use of ZooKeeper, so more lightweight machines or VMs should suffice for running ZooKeeper.

To begin, add all ZooKeeper servers to the configuration specified in conf/zookeeper.conf (in the Pulsar directory that you create ). The following is an example:

server.1=zk1.us-west.example.com:2888:3888
server.2=zk2.us-west.example.com:2888:3888
server.3=zk3.us-west.example.com:2888:3888

If you only have one machine on which to deploy Pulsar, you only need to add one server entry in the configuration file.

On each host, you need to specify the ID of the node in the myid file, which is in the data/zookeeper folder of each server by default (you can change the file location via the dataDir parameter).

See the in the ZooKeeper documentation for detailed information on myid and more.

For example, on a ZooKeeper server like zk1.us-west.example.com, you can set the myid value as follows:

$ mkdir -p data/zookeeper
$ echo 1 > data/zookeeper/myid

On zk2.us-west.example.com, the command is echo 2 > data/zookeeper/myid and so on.

Once you add each server to the zookeeper.conf configuration and have the appropriate myid entry, you can start ZooKeeper on all hosts (in the background, using nohup) with the CLI tool:

$ bin/pulsar-daemon start zookeeper

If you plan to deploy Zookeeper with the Bookie on the same node, you need to start zookeeper by using different stats port.

使用 CLI命令行工具启动zookeeper，如：

初始化集群元数据

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.

You can initialize this metadata using the command of the pulsar CLI tool. This command can be run on any machine in your ZooKeeper cluster. The following is an example:

$ bin/pulsar initialize-cluster-metadata \
  --cluster pulsar-cluster-1 \
  --zookeeper zk1.us-west.example.com:2181 \
  --configuration-store zk1.us-west.example.com:2181 \
  --web-service-url http://pulsar.us-west.example.com:8080 \
  --web-service-url-tls https://pulsar.us-west.example.com:8443 \
  --broker-service-url pulsar://pulsar.us-west.example.com:6650 \
  --broker-service-url-tls pulsar+ssl://pulsar.us-west.example.com:6651

As you can see from the example above, you will need to specify the following:

--web-service-url ,host2:8080,host3:8080
--web-service-url-tls https://host1:8443,host2:8443,host3:8443
--broker-service-url ,host2:6650,host3:6650
--broker-service-url-tls pulsar+ssl://host1:6651,host2:6651,host3:6651

## Deploy a BookKeeper cluster
[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:
```properties
zkServers=zk1.us-west.example.com:2181,zk2.us-west.example.com:2181,zk3.us-west.example.com:2181

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 . However, consulting the BookKeeper documentation 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 , or in the foreground.

$ bin/pulsar-daemon start bookie

To start the bookie in the foreground:

$ bin/bookkeeper bookie

You can verify that a bookie works properly by running the bookiesanity command on the BookKeeper shell:

$ bin/bookkeeper shell bookiesanity

This command creates an ephemeral BookKeeper ledger on the local bookie, writes a few entries, reads them back, and finally deletes the ledger.

After you start all the bookies, you can use simpletest command for on any bookie node, to verify all the bookies in the cluster are up running.

$ bin/bookkeeper shell simpletest --ensemble <num-bookies> --writeQuorum <num-bookies> --ackQuorum <num-bookies> --numEntries <num-entries>

This command creates a num-bookies sized ledger on the cluster, writes a few entries, and finally deletes the ledger.

Pulsar brokers are the last thing you need to deploy in your Pulsar cluster. Brokers handle Pulsar messages and provide the administrative interface of Pulsar. A good choice is to run 3 brokers, one for each machine that already runs a BookKeeper bookie.

The most important element of broker configuration is ensuring that each broker is aware of the ZooKeeper cluster that you have deployed. Ensure that the zookeeperServers and parameters are correct. In this case, since you only have 1 cluster and no configuration store setup, the configurationStoreServers point to the same zookeeperServers.

zookeeperServers=zk1.us-west.example.com:2181,zk2.us-west.example.com:2181,zk3.us-west.example.com:2181
configurationStoreServers=zk1.us-west.example.com:2181,zk2.us-west.example.com:2181,zk3.us-west.example.com:2181

You also need to specify the cluster name (matching the name that you provided when you initialize the metadata of the cluster):

clusterName=pulsar-cluster-1

In addition, you need to match the broker and web service ports provided when you initialize the metadata of the cluster (especially when you use a different port than the default):

If you deploy Pulsar in a one-node cluster, you should update the replication settings in conf/broker.conf to 1.

Number of bookies to use when creating a ledger

managedLedgerDefaultEnsembleSize=1

Number of copies to store for each message

managedLedgerDefaultWriteQuorum=1

Number of guaranteed copies (acks to wait before write is complete)

managedLedgerDefaultAckQuorum=1

### Enable Pulsar Functions (optional)
1. Edit `conf/broker.conf` to enable functions worker, by setting `functionsWorkerEnabled` to `true`.
    functionsWorkerEnabled=true
    ```
2. Edit `conf/functions_worker.yml` and set `pulsarFunctionsCluster` to the cluster name that you provide when you [initialize the metadata of the cluster](#initialize-cluster-metadata).
    ```conf
    pulsarFunctionsCluster: pulsar-cluster-1
    ```
If you want to learn more options about deploying the functions worker, check out [Deploy and manage functions worker](/docs/zh-CN/2.5.2/functions-worker).
### Start Brokers
You can then provide any other configuration changes that you want in the [`conf/broker.conf`](/docs/zh-CN/2.5.2/reference-configuration#broker) file. Once you decide on a configuration, you can start up the brokers for your Pulsar cluster. Like ZooKeeper and BookKeeper, you can start brokers either in the foreground or in the background, using nohup.
You can start a broker in the foreground using the [`pulsar broker`](/docs/zh-CN/2.5.2/reference-cli-tools#pulsar-broker) command:
```bash
$ bin/pulsar broker

You can start a broker in the background using the pulsar-daemon CLI tool:

$ bin/pulsar-daemon start broker

Once you succesfully start up all the brokers that you intend to use, your Pulsar cluster should be ready to go!

Connect to the running cluster

Once your Pulsar cluster is up and running, you should be able to connect with it using Pulsar clients. One such client is the pulsar-client tool, which is included with the Pulsar binary package. The pulsar-client tool can publish messages to and consume messages from Pulsar topics and thus provide a simple way to make sure that your cluster runs properly.

To use the pulsar-client tool, first modify the client configuration file in in your binary package. You need to change the values for webServiceUrl and brokerServiceUrl, substituting localhost (which is the default), with the DNS name that you assign to your broker/bookie hosts. The following is an example:

webServiceUrl=http://us-west.example.com:8080
brokerServiceurl=pulsar://us-west.example.com:6650

If you do not have a DNS server, you can specify multi-host in service URL as follows:

webServiceUrl=http://host1:8080,host2:8080,host3:8080 brokerServiceurl=,host2:6650,host3:6650

Once that is complete, you can publish a message to the Pulsar topic:
```bash
$ bin/pulsar-client produce \
  persistent://public/default/test \
  -n 1 \
  -m "Hello Pulsar"

You may need to use a different cluster name in the topic if you specify a cluster name other than pulsar-cluster-1.

This command publishes a single message to the Pulsar topic. In addition, you can subscribe to the Pulsar topic in a different terminal before publishing messages as below:

$ bin/pulsar-client consume \
  persistent://public/default/test \
  -n 100 \
  -s "consumer-test" \
  -t "Exclusive"

Once you successfully publish the above message to the topic, you should see it in the standard output:

----- 收到消息 -----
Hello Pulsar

Run Functions

If you have Pulsar Functions, you can try out the Pulsar Functions now.

Create an ExclamationFunction exclamation.

bin/pulsar-admin functions create \
  --jar examples/api-examples.jar \
  --classname org.apache.pulsar.functions.api.examples.ExclamationFunction \
  --inputs persistent://public/default/exclamation-input \
  --output persistent://public/default/exclamation-output \
  --tenant public \
  --namespace default \

Check whether the function runs as expected by triggering the function.

bin/pulsar-admin functions trigger --name exclamation --trigger-value "hello world"