pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] merlimat closed pull request #3152: [website][doc] Update the deployment documentation on how to deploy Pulsar to one node
Date Mon, 10 Dec 2018 17:21:52 GMT
merlimat closed pull request #3152: [website][doc] Update the deployment documentation on how
to deploy Pulsar to one node
URL: https://github.com/apache/pulsar/pull/3152

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/site2/docs/deploy-bare-metal.md b/site2/docs/deploy-bare-metal.md
index 3669af9541..af14062377 100644
--- a/site2/docs/deploy-bare-metal.md
+++ b/site2/docs/deploy-bare-metal.md
@@ -29,13 +29,16 @@ Deploying a Pulsar cluster involves doing the following (in order):
 > If you already have an existing zookeeper cluster and would like to reuse it, you don't
need to prepare the machines
 > for running ZooKeeper.
-To run Pulsar on bare metal, you will need:
+To run Pulsar on bare metal, you are recommended to have:
 * At least 6 Linux machines or VMs
   * 3 running [ZooKeeper](https://zookeeper.apache.org)
   * 3 running a Pulsar broker, and a [BookKeeper](https://bookkeeper.apache.org) bookie
 * A single [DNS](https://en.wikipedia.org/wiki/Domain_Name_System) name covering all of the
Pulsar broker hosts
+> However if you don't have enough machines, or are trying out Pulsar in cluster mode
(and expand the cluster later),
+> you can even deploy Pulsar in one node, where it will run zookeeper, bookie and broker
in same machine.
 Each machine in your cluster will need to have [Java 8](http://www.oracle.com/technetwork/java/javase/downloads/index.html)
or higher installed.
 Here's a diagram showing the basic setup:
@@ -148,6 +151,8 @@ server.2=zk2.us-west.example.com:2888:3888
+> If you have only one machine to deploy Pulsar, you just need to add one server entry
in the configuration file.
 On each host, you need to specify the ID of the node in each node's `myid` file, which is
in each server's `data/zookeeper` folder by default (this can be changed via the [`dataDir`](reference-configuration.md#zookeeper-dataDir)
 > See the [Multi-server setup guide](https://zookeeper.apache.org/doc/r3.4.10/zookeeperAdmin.html#sc_zkMulitServerSetup)
in the ZooKeeper documentation for detailed info on `myid` and more.
@@ -268,6 +273,19 @@ You also need to specify the cluster name (matching the name that you
provided w
+> If you deploy Pulsar in a one-node cluster, you should update the replication settings
in `conf/broker.conf` to `1`
+> ```properties
+> # 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
+> ```
 ### Enabling Pulsar Functions (optional)
 If you want to enable [Pulsar Functions](functions-overview.md), you can follow the instructions
as below:


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message