It was still the same problem. For some reason EC2 ubuntu instance was binding Kafka brokers with 127.0.1.1 address. I set the hostname and restarted all the brokers and it worked.
Thanks, Vaibhav On Fri, Apr 27, 2012 at 4:20 PM, Vaibhav Puranik <vpura...@gmail.com> wrote: > Jun, > > Since all the concerned servers (brokers and producers) are on EC2 I > thought this won't apply to me. Internal IP should work within EC2, right? > > Regards, > Vaibhav > > > On Fri, Apr 27, 2012 at 4:04 PM, Jun Rao <jun...@gmail.com> wrote: > >> It seems that you are using ZK-based producer. You may want to look at >> item >> 2 in http://incubator.apache.org/kafka/faq.html. That problem applies to >> the producer too if ZK is used. >> >> Thanks, >> >> Jun >> >> On Fri, Apr 27, 2012 at 2:45 PM, Vaibhav Puranik <vpura...@gmail.com> >> wrote: >> >> > HI all, >> > >> > We are trying out Kafka currently. We are running Kafka 0.7 on 3 EC2 >> > instances (c1.xlarge) with one zookeeper. >> > The clients and servers both are on EC2. >> > >> > Here is what we are getting : >> > >> > >> > 1. java.nio.channels.ClosedChannelException >> > 2. at >> > >> sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:126) >> > 3. at >> > sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:324) >> > 4. at >> > >> > >> kafka.network.BoundedByteBufferSend.writeTo(BoundedByteBufferSend.scala:48) >> > >> > >> > The full exception is here: >> > >> > http://pastebin.com/TnypFpCY >> > >> > >> > The Kafka broker logs doesn't have anything unusual - It's as if the >> > requests are not even reaching to Kafka. >> > >> > Any pointers? >> > >> > Regards, >> > Vaibhav Puranik >> > GumGum >> > >> > >
