On Thu, Nov 29, 2012 at 10:46 AM, Sybrandy, Casey
<casey.sybra...@six3systems.com> wrote:
> Re-sending since I didn't get any responses before and want to make
> sure this made it to the correct group.

>>We're having an issue with Zookeeper, which has nothing to do with
>>Kafka, but my consumers don't appear to be attempting to connect
>>with the two nodes that are up.  I specify my zk.connect as such:
>>host1:2181,host2:2181,host3:2181.
>>
>> Is this correct?  Should this work?  I didn't see anything in the
>> Quick Start to contradict this, so I'm a bit confused.

I think that's correct.  For example, with my test setup I can connect
to our zookeeper cluster and see that /brokers/ids/0 exists, which I
believe corresponds to the brokerid, and I can see a list of topics
(in our case this is just a development environment, so we've got
three instances of zookeeper on the same machine, using different
ports):

$ ./zk_lp_config.pl --zk
logproc-dev-03:2181,logproc-dev-03:2182,logproc-dev-03:2183 ls
/brokers
/brokers/topics
/brokers/ids

$ ./zk_lp_config.pl --zk
logproc-dev-03:2181,logproc-dev-03:2182,logproc-dev-03:2183 ls
/brokers/ids
/brokers/ids/0

$ ./zk_lp_config.pl --zk
logproc-dev-03:2181,logproc-dev-03:2182,logproc-dev-03:2183 ls
/brokers/topics
/brokers/topics/h10-accessdenied-log
/brokers/topics/h20classic-service-log
/brokers/topics/h20classic-accessdenied-log
/brokers/topics/h20-service-log
/brokers/topics/h20classic-apache-access-log
/brokers/topics/h10-apache-access-log
/brokers/topics/h
/brokers/topics/h10-seataccess-log

I believe the /brokers/ids/0 corresponds to the brokerid that one sets
in the configuration file:

  
/usr/local/kafka/kafka-0.7.0-incubating-src/config/server.properties:brokerid=0

For my kafka startup I point to the zookeeper "cluster" like so:

  --kafka-zk-connect logproc-dev-03:2181,logproc-dev-03:2182,logproc-dev-03:2183

Jim

Reply via email to