This may be due to a bug in 0.7.1 with respect to ZK based producer. Could you try sending 1 produce request to the new broker directly first and then try the ZK based producer?
Thanks, Jun On Tue, Sep 11, 2012 at 9:41 AM, Mark Grabois <mark.grab...@trendrr.com>wrote: > I think it's a broker issue. The producers are connected to the zookeeper > running on the node, and currently they are producing messages correctly to > the other nodes. > > On Mon, Sep 10, 2012 at 11:32 PM, Jun Rao <jun...@gmail.com> wrote: > > > Mark, > > > > Is this a broker side issue or a producer side issue? > > > > Thanks, > > > > Jun > > > > On Mon, Sep 10, 2012 at 9:23 AM, Mark Grabois <mark.grab...@trendrr.com > > >wrote: > > > > > Hi All, > > > > > > Currently I have two nodes with both zookeeper and kafka instances > > running > > > successfully, processing messages with connections to both producer and > > > consumer clients. However, when I try to add a third kafka+zk node to > the > > > quorum, configured in the exact same way and having specified all > broker > > > ids and server ips properly, kafka is unable to establish a connection > to > > > my producers on the default listening port (9092). Zookeeper appears to > > be > > > connecting properly to the cluster, but not Kafka. > > > > > > Any recommendations on how to troubleshoot this? All nodes are running > > > kafka-0.7.1. > > > > > > Thank you, > > > Mark > > > > > >
