Anonymitaet commented on a change in pull request #5135: [doc] Improve Pulsar deployment bare metal multi cluster URL: https://github.com/apache/pulsar/pull/5135#discussion_r321736637
########## File path: site2/docs/deploy-bare-metal-multi-cluster.md ########## @@ -6,34 +6,34 @@ sidebar_label: Bare metal multi-cluster > ### Tips > -> 1. Single-cluster Pulsar installations should be sufficient for all but the most ambitious use cases. If you're interested in experimenting with -> Pulsar or using it in a startup or on a single team, we recommend opting for a single cluster. For instructions on deploying a single cluster, +> 1. Single-cluster Pulsar installations should be sufficient for all but the most ambitious use cases. If you are interested in experimenting with +> Pulsar or using it in a startup or on a single team, you had better opt for a single cluster. For instructions on deploying a single cluster, > see the guide [here](deploy-bare-metal.md). > > 2. If you want to use all builtin [Pulsar IO](io-overview.md) connectors in > your Pulsar deployment, you need to download `apache-pulsar-io-connectors` -> package and make sure it is installed under `connectors` directory in the pulsar directory on every broker node or on every function-worker node if you -> have run a separate cluster of function workers for [Pulsar Functions](functions-overview.md). +> package and install `apache-pulsar-io-connectors` under `connectors` directory in the pulsar directory on every broker node or on every function-worker node if you +> run a separate cluster of function workers for [Pulsar Functions](functions-overview.md). > > 3. If you want to use [Tiered Storage](concepts-tiered-storage.md) feature > in your Pulsar deployment, you need to download `apache-pulsar-offloaders` -> package and make sure it is installed under `offloaders` directory in the pulsar directory on every broker node. For more details of how to configure -> this feature, you could reference this [Tiered storage cookbook](cookbooks-tiered-storage.md). +> package and install `apache-pulsar-offloaders` under `offloaders` directory in the pulsar directory on every broker node. For more details of how to configure +> this feature, you can refer to the [Tiered storage cookbook](cookbooks-tiered-storage.md). -A Pulsar *instance* consists of multiple Pulsar clusters working in unison. Clusters can be distributed across data centers or geographical regions and can replicate amongst themselves using [geo-replication](administration-geo.md). Deploying a multi-cluster Pulsar instance involves the following basic steps: +A Pulsar *instance* consists of multiple Pulsar clusters working in unison. You can distribute clusters across data centers or geographical regions and replicate the clusters amongst themselves using [geo-replication](administration-geo.md). Deploying a multi-cluster Pulsar instance involves the following basic steps: * Deploying two separate [ZooKeeper](#deploying-zookeeper) quorums: a [local](#deploying-local-zookeeper) quorum for each cluster in the instance and a [configuration store](#configuration-store) quorum for instance-wide tasks * Initializing [cluster metadata](#cluster-metadata-initialization) for each cluster * Deploying a [BookKeeper cluster](#deploying-bookkeeper) of bookies in each Pulsar cluster * Deploying [brokers](#deploying-brokers) in each Pulsar cluster -If you're deploying a single Pulsar cluster, see the [Clusters and Brokers](getting-started-standalone.md#starting-the-cluster) guide. +If you want to deploy a single Pulsar cluster, see the [Clusters and Brokers](getting-started-standalone.md#starting-the-cluster) for a guide. Review comment: ```suggestion If you want to deploy a single Pulsar cluster, see [Clusters and Brokers](getting-started-standalone.md#starting-the-cluster). ``` ---------------------------------------------------------------- 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
