Re: FW: Zookeeper Configuration Question
If you're using the zkCli.sh, something like this will create the namespace: [zk: localhost:12913(CONNECTED) 1] create /namespace '' Created /namespace If you're using another interface, the actual command may vary. -- Dave DeMaagd ddema...@linkedin.com | 818 262 7958 (casey.sybra...@six3systems.com - Mon, Dec 10, 2012 at 01:49:32PM +) > Apologies for not responding sooner. My mail client must have been > malfunctioning at the time as I never saw your responses until today. > > As for the error, it looks like it's a bug on my part that just didn't click > until I read Jim's responses. I have a config file that I specify the > options in and I copied it from a Configuration object to a Properties > object, as the producer/consumer requires. Didn't realize until this morning > that it was not working as expected. > > On a different note: does anyone know how to create a namespace in Zookeeper? > We're having some issues I'm trying to debug so I want to isolate some of > our brokers, but finding documentation on this has been fruitless. > > Thanks! > > From: Neha Narkhede [neha.narkh...@gmail.com] > Sent: Thursday, November 29, 2012 4:39 PM > To: users@kafka.apache.org > Subject: Re: FW: Zookeeper Configuration Question > > Please can you send around the log that shows the zookeeper connection > error ? I would like to see if it fails at connection establishment or > session establishment. > > Thanks, > Neha > > On Thu, Nov 29, 2012 at 1:19 PM, James A. Robinson > wrote: > > On Thu, Nov 29, 2012 at 1:15 PM, James A. Robinson > > wrote: > >> 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 > > > > Sorry, wrong copy and paste! For the kafka startup I point to the zookeeper > > cluster like so (in the properties file): > > > > zk.connect=logproc-dev-03.highwire.org:2181,logproc-dev-03.highwire.org:2182,logproc-dev-03.highwire.org:2183
RE: FW: Zookeeper Configuration Question
Apologies for not responding sooner. My mail client must have been malfunctioning at the time as I never saw your responses until today. As for the error, it looks like it's a bug on my part that just didn't click until I read Jim's responses. I have a config file that I specify the options in and I copied it from a Configuration object to a Properties object, as the producer/consumer requires. Didn't realize until this morning that it was not working as expected. On a different note: does anyone know how to create a namespace in Zookeeper? We're having some issues I'm trying to debug so I want to isolate some of our brokers, but finding documentation on this has been fruitless. Thanks! From: Neha Narkhede [neha.narkh...@gmail.com] Sent: Thursday, November 29, 2012 4:39 PM To: users@kafka.apache.org Subject: Re: FW: Zookeeper Configuration Question Please can you send around the log that shows the zookeeper connection error ? I would like to see if it fails at connection establishment or session establishment. Thanks, Neha On Thu, Nov 29, 2012 at 1:19 PM, James A. Robinson wrote: > On Thu, Nov 29, 2012 at 1:15 PM, James A. Robinson > wrote: >> 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 > > Sorry, wrong copy and paste! For the kafka startup I point to the zookeeper > cluster like so (in the properties file): > > zk.connect=logproc-dev-03.highwire.org:2181,logproc-dev-03.highwire.org:2182,logproc-dev-03.highwire.org:2183
Re: FW: Zookeeper Configuration Question
Please can you send around the log that shows the zookeeper connection error ? I would like to see if it fails at connection establishment or session establishment. Thanks, Neha On Thu, Nov 29, 2012 at 1:19 PM, James A. Robinson wrote: > On Thu, Nov 29, 2012 at 1:15 PM, James A. Robinson > wrote: >> 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 > > Sorry, wrong copy and paste! For the kafka startup I point to the zookeeper > cluster like so (in the properties file): > > zk.connect=logproc-dev-03.highwire.org:2181,logproc-dev-03.highwire.org:2182,logproc-dev-03.highwire.org:2183
Re: FW: Zookeeper Configuration Question
On Thu, Nov 29, 2012 at 1:15 PM, James A. Robinson wrote: > 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 Sorry, wrong copy and paste! For the kafka startup I point to the zookeeper cluster like so (in the properties file): zk.connect=logproc-dev-03.highwire.org:2181,logproc-dev-03.highwire.org:2182,logproc-dev-03.highwire.org:2183
Re: FW: Zookeeper Configuration Question
On Thu, Nov 29, 2012 at 10:46 AM, Sybrandy, Casey 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
