You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/08/20 03:00:09 UTC
[GitHub] [pulsar] Anonymitaet commented on a change in pull request #11712: [docs] [ISSUE 8671] Add hardware settings recommendations
Anonymitaet commented on a change in pull request #11712:
URL: https://github.com/apache/pulsar/pull/11712#discussion_r692623364
##########
File path: site2/docs/getting-started-standalone.md
##########
@@ -4,25 +4,56 @@ title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
---
-For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.
+## Preparation
-> #### Pulsar in production?
-> If you're looking to run a full production Pulsar installation, see the [Deploying a Pulsar instance](deploy-bare-metal.md) guide.
+### Requirements
-## Install Pulsar standalone
+Currently, Pulsar is available for 64-bit **macOS**, **Linux**, and **Windows**. To use Pulsar, you need to install 64-bit JRE/JDK 8 or later versions.
-This tutorial guides you through every step of the installation process.
+> **Note**
+> Broker is only supported on 64-bit JVM.
-### System requirements
+> **Tip**
+> By default, Pulsar allocates 2G JVM heap memory to start. It can be changed in `conf/pulsar_env.sh` file under `PULSAR_MEM`. This is extra options passed into JVM.
-Currently, Pulsar is available for 64-bit **macOS**, **Linux**, and **Windows**. To use Pulsar, you need to install 64-bit JRE/JDK 8 or later versions.
+For local development and testing, you can run Pulsar in standalone mode on your machine. The standalone mode includes a Pulsar broker, the necessary ZooKeeper and BookKeeper components running inside of a single Java Virtual Machine (JVM) process.
-> #### Tip
-> By default, Pulsar allocates 2G JVM heap memory to start. It can be changed in `conf/pulsar_env.sh` file under `PULSAR_MEM`. This is extra options passed into JVM.
+> **Note**
+> You can reuse existing Zookeeper clusters.
-> **Note**
->
-> Broker is only supported on 64-bit JVM.
+> **Pulsar in production?**
+> If you're looking to run a full production Pulsar installation, see the [Deploying a Pulsar instance](deploy-bare-metal.md) guide.
+
+### Hardware considerations
Review comment:
Why need to add hardware considerations (which are usually added to the `deployment` chapter ) to the `getting started` guide?
--
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.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org