Jennifer88huang commented on a change in pull request #8269: URL: https://github.com/apache/pulsar/pull/8269#discussion_r505617450
########## File path: site2/docs/deploy-bare-metal.md ########## @@ -253,6 +253,17 @@ Flag | Description > --broker-service-url-tls pulsar+ssl://host1:6651,host2:6651,host3:6651 > ``` +> If you want to use an existing BookKeeper cluster, you can add `--existing-bk-metadata-service-uri` flag at the mean time like below: +> +> ```properties +> --existing-bk-metadata-service-uri "zk+null://bk1:2181;bk2:2181/ledgers" \ +> --web-service-url http://host1:8080,host2:8080,host3:8080 \ +> --web-service-url-tls https://host1:8443,host2:8443,host3:8443 \ +> --broker-service-url pulsar://host1:6650,host2:6650,host3:6650 \ +> --broker-service-url-tls pulsar+ssl://host1:6651,host2:6651,host3:6651 +> ``` +> The metadata service uri of existing BookKeeper cluster can be fetched via `bin/bookkeeper shell whatisinstanceid` command. Note that the value need to be enclosed in double quotes since the multi metadata service uri is semicolon separated. Review comment: ```suggestion > You can obtain the metadata service URI of the existing BookKeeper cluster by using the `bin/bookkeeper shell whatisinstanceid` command. You must enclose the value in double quotes since the multiple metadata service URIs are separated with semicolons. ``` ---------------------------------------------------------------- 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]
