lhotari commented on PR #24665: URL: https://github.com/apache/pulsar/pull/24665#issuecomment-3222943292
It's great that we are finally resolving this issue. *Workaround for ZooKeeper, by-passing the Pulsar Metadata driver for BookKeeper client and BookKeeper server-side components*: I faced this a few years ago. As a workaround at that time I introduced a way to by-pass the use of Pulsar Metadata Drivers in BookKeepers with this change: #17834. That prevents loading the drivers. In addition to that, it's possible to configure BookKeeper to use direct ZK access without Pulsar Metadata Drivers. On the Broker (BookKeeper client), this requires setting `bookkeeperMetadataServiceUri: "zk+hierarchical://.."` and on BookKeeper components it's possible to set `metadataServiceUri: "zk+hierarchical://...` (and set the legacy values `zkServers` and `zkLedgersRootPath` to empty values since `metadataServiceUri` is the recommended way after [BP-29](https://bookkeeper.apache.org/bps/BP-29-metadata-store-api-module). -- 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-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
