jarleaase commented on issue #9861: URL: https://github.com/apache/pulsar/issues/9861#issuecomment-795530209
Hi, I am working on a distributed cloud app where Pulsar is one of many components. In production, Pulsar is deployed with Helm Charts. For my local development setup, I need to test and debug my components, and they use Pulsar. Therefore, I have been deploying Pulsar standalone, as this is pretty straight forward. It has worked fine for a long time - both with docker-compose and kubernetes. Now, I am working on the code related to distributed processing, and I need to deploy (locally) several clusters. That means that the Pulsar cluster names cannot all be "standalone". I prefer to *use* the standalone alternative for development, because it's faster to deploy and simpler to use. As a work-around for now, I am deploying a normal Pulsar with zookeeper, bookkeeper and broker, each with 1 instance, using a custom built deployer. But still, it would be nice if standalone Pulsar let me specify the cluster name. The option is documented, so when it don't work, I assume it is a bug :) ---------------------------------------------------------------- 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]
