lhotari opened a new pull request, #17834:
URL: https://github.com/apache/pulsar/pull/17834

   ### Motivation
   
   PIP-45 related PRs #12770 and #13296 introduced changes in Pulsar and 
Bookkeeper configuration for Pulsar so that Pulsar Metadata driver is used for 
metadata operations in the bookkeeper client (in broker) and in the bookkeeper 
server (the bookies).
   It would be good to have a way to opt-out of this change and configure 
Pulsar and Bookies without Pulsar Metadata store and use Zookeeper directly. 
   
   This PR will allow to use Bookkeeper defaults by setting `export 
BK_METADATA_OPTIONS=none`.
   
   If one would want to configure Bookies without Pulsar Metadata, it is 
necessary to configure
   `metadataServiceUri` in bookkeeper.conf and `bookkeeperMetadataServiceUri` 
in broker.conf.
   
   For example `bookkeeper.conf`
   ```properties
   
metadataServiceUri=zk://<zk_node_1>:2181/ledgers,zk://<zk_node_2>:2181/ledgers,zk://<zk_node_3>:2181/ledgers
   ```
   
   The main purpose of this PR is to make it easier to compare the behavior of 
Pulsar when using Pulsar Metadata driver for Bookkeeper compared to using 
Zookeeper directly. It is not necessary make BK_METADATA_OPTIONS configurable 
to achieve this. However it's better to have an option to control it since that 
could prevent misconfiguration in cases where it is desired to not use Pulsar 
metadata driver. 
   
   
   ### Modifications
   
   Make `BK_METADATA_OPTIONS` configurable.
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc-required` 
   (Your PR needs to update docs and you will update later)
   
   - [x] `doc-not-needed` 
   (Please explain why)
   
   - [ ] `doc` 
   (Your PR contains doc changes)
   
   - [ ] `doc-complete`
   (Docs have been already added)
   
   ### Matching PR in forked repository
   
   PR in forked repository: 


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to