You can try to debug the issue with simple command line tools, like
"pulsar-client" or "pulsar-perf".
Example and reference is here:
On Fri, Aug 18, 2017 at 10:55 AM J.R. Pauley wrote:
> Thanks. Only reason
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 wrote:
> You can certainly use the Pulsar standalone
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,
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?
On Wed, Aug 9, 2017 at 2:47 PM, Matteo Merli wrote:
> So, for quick tests with the pulsar-standalone
So, for quick tests with the pulsar-standalone there's no need to worry
ZooKeeper, since it's providing everything out of the box.
So, you need to deploy a ZK cluster or connect to an existing one only if
to deploy a multi-node Pulsar cluster, with "real" brokers and bookies.
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