the Pulsar standalone is a self-contained Pulsar instance and it starts
everything it needs, within a single JVM, the broker, BookKeeper and
It is meant to be used for testing or anywhere availability, replication
and scalability are not a concern.
By default the standalone logs are printed in the console.
You can use:
bin/pulsar-daemon start standalone
to start it in background with logs redirected to a file. In any case, just
modify the "conf/log4j.properties" for the logging configuration.
On Tue, Aug 8, 2017 at 5:37 AM J.R. Pauley <jrpau...@gmail.com> wrote:
> Regarding the config files for zookeeper etc, are the defaults meant to
> work or need changing?
> I'm not locating any pulsar-standalone.log and checking ps no zookeeper is
> started by default from bin/pulsar standalone.
> I'm guessing I need to start zookeeper separately. No idea about
> bookkeeper etc. The Gettign Started info is a bit sparse and contains a few
> 404's also.
> My goal is to try out storm adaptors and I already have a running
> storm/zookeeper, but not a good start when I can't get the Hello example to
> produce a log.
> Any quick tips?