This is an automated email from the ASF dual-hosted git repository. visortelle pushed a commit to branch pulsar-standalone in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
commit 7b9decb725df72c7408888c9d5d0c1d5ab33bec9 Author: visortelle <[email protected]> AuthorDate: Fri Mar 29 17:18:55 2024 +0400 Recommend ZK for Pulsar standalone --- docs/getting-started-docker-compose.md | 3 ++- docs/getting-started-docker.md | 18 ++++++++++++++++++ versioned_docs/version-3.0.x/getting-started-docker.md | 18 ++++++++++++++++++ .../version-3.2.x/getting-started-docker-compose.md | 3 ++- versioned_docs/version-3.2.x/getting-started-docker.md | 18 ++++++++++++++++++ 5 files changed, 58 insertions(+), 2 deletions(-) diff --git a/docs/getting-started-docker-compose.md b/docs/getting-started-docker-compose.md index 9af7c3770a52..b3048013c5dd 100644 --- a/docs/getting-started-docker-compose.md +++ b/docs/getting-started-docker-compose.md @@ -114,10 +114,11 @@ services: ## Step 2: Create a Pulsar cluster As preparation, create data directories and change the data directory ownership to uid(10000) which is the default user id used in the Pulsar Docker container. + ```bash sudo mkdir -p ./data/zookeeper ./data/bookkeeper # this step might not be necessary on other than Linux platforms -sudo chown 10000 -R data +sudo chown -R 10000 data ``` To create a Pulsar cluster by using the `compose.yml` file, run the following command. diff --git a/docs/getting-started-docker.md b/docs/getting-started-docker.md index 785fb8f9037e..799568e99c95 100644 --- a/docs/getting-started-docker.md +++ b/docs/getting-started-docker.md @@ -56,6 +56,24 @@ bin/pulsar standalone </Tabs> ```` +:::tip + +You may encounter issues with the default RocksDB metadata store after restarting Pulsar standalone. + +Tracking issue: [#21421](https://github.com/apache/pulsar/issues/21421) + +We recommend you consider using the following environment variable to use ZooKeeper as the metadata store: + +``` +... +-e PULSAR_STANDALONE_USE_ZOOKEEPER=1 \ +... +``` + +Don't apply this fix for existing Pulsar standalone instances if you don't want to loose your data. + +::: + If you want to change Pulsar configurations and start Pulsar, run the following command by passing environment variables with the `PULSAR_PREFIX_` prefix. See [default configuration file](https://github.com/apache/pulsar/blob/e6b12c64b043903eb5ff2dc5186fe8030f157cfc/conf/standalone.conf) for more details. ````mdx-code-block diff --git a/versioned_docs/version-3.0.x/getting-started-docker.md b/versioned_docs/version-3.0.x/getting-started-docker.md index e8d706f0f7ca..92c74aa5d04b 100644 --- a/versioned_docs/version-3.0.x/getting-started-docker.md +++ b/versioned_docs/version-3.0.x/getting-started-docker.md @@ -16,6 +16,24 @@ For macOS, Linux, and Windows, run the following command to start Pulsar within docker run -it -p 6650:6650 -p 8080:8080 --mount source=pulsardata,target=/pulsar/data --mount source=pulsarconf,target=/pulsar/conf apachepulsar/pulsar:@pulsar:version@ bin/pulsar standalone ``` +:::tip + +You may encounter issues with the default RocksDB metadata store after restarting Pulsar standalone. + +Tracking issue: [#21421](https://github.com/apache/pulsar/issues/21421) + +We recommend you consider using the following environment variable to use ZooKeeper as the metadata store: + +``` +... +-e PULSAR_STANDALONE_USE_ZOOKEEPER=1 \ +... +``` + +Don't apply this fix for existing Pulsar standalone instances if you don't want to loose your data. + +::: + If you want to change Pulsar configurations and start Pulsar, run the following command by passing environment variables with the `PULSAR_PREFIX_` prefix. See [default configuration file](https://github.com/apache/pulsar/blob/e6b12c64b043903eb5ff2dc5186fe8030f157cfc/conf/standalone.conf) for more details. ```shell diff --git a/versioned_docs/version-3.2.x/getting-started-docker-compose.md b/versioned_docs/version-3.2.x/getting-started-docker-compose.md index 9af7c3770a52..b3048013c5dd 100644 --- a/versioned_docs/version-3.2.x/getting-started-docker-compose.md +++ b/versioned_docs/version-3.2.x/getting-started-docker-compose.md @@ -114,10 +114,11 @@ services: ## Step 2: Create a Pulsar cluster As preparation, create data directories and change the data directory ownership to uid(10000) which is the default user id used in the Pulsar Docker container. + ```bash sudo mkdir -p ./data/zookeeper ./data/bookkeeper # this step might not be necessary on other than Linux platforms -sudo chown 10000 -R data +sudo chown -R 10000 data ``` To create a Pulsar cluster by using the `compose.yml` file, run the following command. diff --git a/versioned_docs/version-3.2.x/getting-started-docker.md b/versioned_docs/version-3.2.x/getting-started-docker.md index 785fb8f9037e..799568e99c95 100644 --- a/versioned_docs/version-3.2.x/getting-started-docker.md +++ b/versioned_docs/version-3.2.x/getting-started-docker.md @@ -56,6 +56,24 @@ bin/pulsar standalone </Tabs> ```` +:::tip + +You may encounter issues with the default RocksDB metadata store after restarting Pulsar standalone. + +Tracking issue: [#21421](https://github.com/apache/pulsar/issues/21421) + +We recommend you consider using the following environment variable to use ZooKeeper as the metadata store: + +``` +... +-e PULSAR_STANDALONE_USE_ZOOKEEPER=1 \ +... +``` + +Don't apply this fix for existing Pulsar standalone instances if you don't want to loose your data. + +::: + If you want to change Pulsar configurations and start Pulsar, run the following command by passing environment variables with the `PULSAR_PREFIX_` prefix. See [default configuration file](https://github.com/apache/pulsar/blob/e6b12c64b043903eb5ff2dc5186fe8030f157cfc/conf/standalone.conf) for more details. ````mdx-code-block
