[GitHub] [bookkeeper] eolivelli commented on a change in pull request #2576: [Doc] Add descriptions for BookKeeper metadata store

[GitBox <gi...@apache.org>]

eolivelli commented on a change in pull request #2576:
URL: https://github.com/apache/bookkeeper/pull/2576#discussion_r568379524



##########
File path: site/docs/latest/getting-started/concepts.md
##########
@@ -76,7 +76,7 @@ The NameNode, however, served only as initial inspiration for BookKeeper. The ap
 
 ## Metadata storage
 
-BookKeeper requires a metadata storage service to store information related to [ledgers](#ledgers) and available bookies. BookKeeper currently uses [ZooKeeper](https://zookeeper.apache.org) for this and other tasks.
+The BookKeeper metadata store maintains all the metadata of the BookKeeper cluster, such as [ledger](#ledgers) metadata, available bookies, and so on. Currently, BookKeeper uses [ZooKeeper](https://zookeeper.apache.org) for  metadata storage. You can use one Zookeeper cluster for both BookKeeper metadata store and [Pulsar metadata store](https://pulsar.apache.org/docs/en/next/concepts-architecture-overview/#metadata-store). If you want to deploy Pulsar brokers connected to an existing BookKeeper cluster, you need to deploy separate ZooKeeper clusters for Pulsar metadata store and BookKeeper metadata store respectively.

Review comment:
       I am not sure we need to add here in BK website this reference to Pulsar.
   
   Can you please explain why do we need this correction?
   Can't we write it in Pulsar website?




----------------------------------------------------------------
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:
users@infra.apache.org