Jason918 commented on pull request #12776:
URL: https://github.com/apache/pulsar/pull/12776#issuecomment-968818840
@eolivelli
> RocksDB is only local, so you could use this mostly only for Pulsar
Standalone.
Yes, that's plan. This is one of multi-step work for Pulsar Standalone.
> Why should I use RocksDB and not ZooKeeper for Pulsar Standalone ?
IMHO, in Pulsar Standalone, we already have RocksDb in dependency, so by
removing zk from standalone mode, we can make it more lightweight, **with less
running memory consumption and less time of starting up.** Although pulsar
standalone is not for production use, it's quite useful and important for
offline developing, testing and CI/CD.
> Also we should state clearly that using this implementation is not
possible for production usage because each broker will have its own copy of the
data, as RocksDB is not a distributed database.
Yes, more detailed doc will be added later, since there is some more work to
achieve this, like "Bridge BookKeeper metadata into MetadataStore"...
@merlimat @codelipenghui @hangc0276 Do we have more detailed doc for this
(Removing zk from Pulsar standalone)?
--
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]
