Anonymitaet commented on a change in pull request #6181: Changes to improve readability URL: https://github.com/apache/pulsar/pull/6181#discussion_r380672093
########## File path: site2/docs/deploy-bare-metal.md ########## @@ -33,37 +33,37 @@ Deploying a Pulsar cluster involves doing the following (in order): > 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, you had better have the following: +To run Pulsar on bare metal, the following configuration is recommended: * At least 6 Linux machines or VMs * 3 for running [ZooKeeper](https://zookeeper.apache.org) * 3 for 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 -> If you do not have enough machines, or try out Pulsar in cluster mode (and expand the cluster later), -> you can even deploy Pulsar in one node, where Zookeeper, bookie and broker are run in the same machine. +> 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 multi-host in service URL instead. +> 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 [Java 8](http://www.oracle.com/technetwork/java/javase/downloads/index.html) or higher version of Java installed. +Each machine in your cluster needs to have [Java 8](http://www.oracle.com/technetwork/java/javase/downloads/index.html) 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 message brokers run on machines alongside BookKeeper bookies; brokers and bookies, in turn, rely on ZooKeeper. +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 message brokers run on machines alongside BookKeeper bookies; brokers and bookies, in turn, rely on ZooKeeper. ### Hardware considerations 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, you had better use lighter-weight machines or VMs. Pulsar uses ZooKeeper only for periodic coordination-related and configuration-related tasks, *not* for basic operations. If you run Pulsar on [Amazon Web Services](https://aws.amazon.com/) (AWS), for example, a [t2.small](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/t2-instances.html) instance might likely suffice. +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 [Amazon Web Services](https://aws.amazon.com/) (AWS), for example, a [t2.small](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/t2-instances.html) instance might likely suffice. Review comment: it is recommended to... Why uses "less powerful" rather than "light-weight"? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
