There was a mistake in my code and now the topology is using the external
zookeeper. But I still see the message
No partition information found, using configuration to determine offset
I don't know the significance of this message. My main objective is to find
out why kafka spout is so slow.
than
Hi,
Even if I use the local cluster with the constructor that specified the
external zookeeper's address, I still see:
backtype.storm.zookeeper - Starting inprocess zookeeper at port 2000
and
org.apache.storm.zookeeper.ZooKeeper - Initiating client connection,
connectString=localhost:2000 sessionT
LocalCluster should be used for debugging a topology . There is another
constructor you can use
LocalCluster cluster = new LocalCluster("localhost", new Long(2182));
first param is zookeeper host and second is the port.
-Harsha
On Tue, Feb 3, 2015, at 07:48 PM, Shivendra Singh wrote:
> Hi Clay,
>
Hi Clay,
The zookeeper info provided to KafkaSpout is external zookeeper which is used
by Kafka and where all the host/partition information for Kafka is stored.
When you run storm in local mode, it spins up an in-memory zookeeper for storm
where it keeps data related to nimbus/supervisors, etc
Hi,
I have a topology running in local mode. The topology uses kafkaspout and
is configured to use the external zookeeper. But when I start the topology,
I see the following:
org.apache.storm.zookeeper.ZooKeeper - Initiating client connection,
connectString=localhost:2000
I also messages like t
