You can try to debug the issue with simple command line tools, like "pulsar-client" or "pulsar-perf".
Example and reference is here: https://pulsar.incubator.apache.org/docs/latest/reference/CliTools/ On Fri, Aug 18, 2017 at 10:55 AM J.R. Pauley <jrpau...@gmail.com> wrote: > Thanks. Only reason I ask is the exception I posted to Heron group. Trying > to specify config URL http://localhost:6650 or pulsar://localhost:6650 > does not seem to do the trick > > On Fri, Aug 18, 2017 at 1:43 PM, Matteo Merli <mme...@apache.org> wrote: > >> You can certainly use the Pulsar standalone to feed streaming topologies. >> The only constraints of the standalone are more around: >> * Throughput (only 1 broker) >> * Availability (if that machine/process goes down, the "service" is down) >> * Durability (data is stored in a single node, lose one disk, lose the >> data) >> >> Deploying a multi-node clusters with brokers and bookies is a bit more >> involved, and probably not worth it to just do simple tests. >> You can find docs for deploying on bare metal or Kubernetes in >> https://pulsar.incubator.apache.org/docs/latest/deployment/InstanceSetup/ >> >> >> On Fri, Aug 18, 2017 at 9:38 AM J.R. Pauley <jrpau...@gmail.com> wrote: >> >>> is standalone suitable for use w/ Heron and PulsarSpout adaptor or does >>> pulsar need to be started in broker mode? If the latter how do you specify >>> the config file to use? >>> >>> -- >> Matteo Merli >> <mme...@apache.org> >> > > -- Matteo Merli <mme...@apache.org>