Hmm, ok. After shutting down and restarting all four shells (zk, broker, producer, consumer) I get the same entries in the log. My understanding is that the node will be created if not present, but I would expect it to be present after restarting (and not clearing any data.)
-j On May 24, 2012, at 10:21 AM, Neelesh wrote: > I think its normal, AFAIK, zk looks for that node and if not present > creates one. > > On Thu, May 24, 2012 at 9:19 AM, Rodenburg, Jeff <jeff.rodenb...@teamaol.com >> wrote: > >> Hello all - >> >> Just joined the mailing list, and see a similar message to this earlier >> this month, but haven't seen any follow-up on the message. >> >> I just pulled v0.7 and installed it, and am running the quick start, >> straight (no config modifications.) I can run the quick start, sending >> messages from the producer and seeing those retrieved by the consumer. >> >> However, there are exceptions being thrown in the zookeeper server: >> >> [2012-05-24 12:13:59,487] INFO Got user-level KeeperException when >> processing sessionid:0x1377f9f00fa0002 type:create cxid:0x1 >> zxid:0xfffffffffffffffe txntype:unknown reqpath:n/a Error >> Path:/consumers/console-consumer-28722/ids Error:KeeperErrorCode = NoNode >> for /consumers/console-consumer-28722/ids >> (org.apache.zookeeper.server.PrepRequestProcessor) >> [2012-05-24 12:13:59,496] INFO Got user-level KeeperException when >> processing sessionid:0x1377f9f00fa0002 type:create cxid:0x2 >> zxid:0xfffffffffffffffe txntype:unknown reqpath:n/a Error >> Path:/consumers/console-consumer-28722 Error:KeeperErrorCode = NoNode for >> /consumers/console-consumer-28722 >> (org.apache.zookeeper.server.PrepRequestProcessor) >> >> As an aside, I also found this log entry in the start of zookeeper: >> >> [2012-05-24 12:12:35,882] INFO Reading configuration from: >> config/zookeeper.properties >> (org.apache.zookeeper.server.quorum.QuorumPeerConfig) >> [2012-05-24 12:12:35,884] WARN Either no config or no quorum defined in >> config, running in standalone mode >> (org.apache.zookeeper.server.quorum.QuorumPeerMain) >> >> Although it works, this seems incorrect. >> >> Is anyone else encountering this problem? >> >> thanks, >> j