Anonymitaet commented on a change in pull request #5111: [doc] Improve Pulsar 
deployment bare metal
URL: https://github.com/apache/pulsar/pull/5111#discussion_r320779862
 
 

 ##########
 File path: site2/docs/deploy-bare-metal.md
 ##########
 @@ -30,51 +30,51 @@ Deploying a Pulsar cluster involves doing the following 
(in order):
 
 ### Requirements
 
-> If you already have an existing zookeeper cluster and would like to reuse 
it, you don't need to prepare the machines
+> 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 are recommended to have:
+To run Pulsar on bare metal, you had better have the following:
 
 * 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
+  * 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
 
-> 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.
+> 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 don't have a DNS server, you can use multi-host in service URL 
instead.
+> If you do not have a DNS server, you can use multi-host in service URL 
instead.
 
-Each machine in your cluster will need to have [Java 
8](http://www.oracle.com/technetwork/java/javase/downloads/index.html) or 
higher installed.
+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.
 
-Here's a diagram showing the basic setup:
+The following is a diagram showing the basic setup:
 
 ![alt-text](assets/pulsar-basic-setup.png)
 
-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`, that 
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 deploying a Pulsar cluster, we have some basic recommendations that you 
should keep in mind when capacity planning.
+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, we recommend using lighter-weight machines or 
VMs. Pulsar uses ZooKeeper only for periodic coordination- and 
configuration-related tasks, *not* for basic operations. If you're running 
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 would likely suffice.
+For machines running ZooKeeper, you had better use lighter-weight machines or 
VMs. Pulsar uses ZooKeeper only for periodic coordination- 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.
 
-#### Bookies & Brokers
+#### Bookies and Brokers
 
-For machines running a bookie and a Pulsar broker, we recommend using more 
powerful machines. For an AWS deployment, for example, 
[i3.4xlarge](https://aws.amazon.com/blogs/aws/now-available-i3-instances-for-demanding-io-intensive-applications/)
 instances may be appropriate. On those machines we also recommend:
+For machines running a bookie and a Pulsar broker, you had better use more 
powerful machines. For an AWS deployment, for example, 
[i3.4xlarge](https://aws.amazon.com/blogs/aws/now-available-i3-instances-for-demanding-io-intensive-applications/)
 instances may be appropriate. On those machines you had better use the 
following:
 
 Review comment:
   ```suggestion
   For machines running a bookie and a Pulsar broker, you had better use more 
powerful machines. For an AWS deployment, for example, 
[i3.4xlarge](https://aws.amazon.com/blogs/aws/now-available-i3-instances-for-demanding-io-intensive-applications/)
 instances may be appropriate. On those machines you can use the following:
   ```

----------------------------------------------------------------
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

Reply via email to