The issue doesn't seem to point to anything. Do you mind sending it in a pastebin?
On Thu, Oct 10, 2013 at 9:54 PM, Jiang Jacky <jiang0...@gmail.com> wrote: > Hi, Thanks Joe > I have disabled the firewall, but I did not tried that again, I changed > another way by using Netty sending the socket package to kafka server, then > it will produce in the local. But recently I suddenly ran into below issue, > can you have a look? > https://mail.google.com/mail/ca/u/0/#label/TechDiscuss/141a5c074641dd70 > Thanks. > > > 2013/10/10 Joseph Lawson <jlaw...@roomkey.com> > > > another thing to note is that your brokers may be running on port 6667 > > instead of 9092. it appears that the default recently changed from 9092 > to > > 6667 so make sure if you have firewall rules for 9092 that you > specifically > > set the port setting in your configuration to what you expect. -Joe > > > > Sent from my Droid Charge on Verizon 4G LTE Joseph Lawson wrote: > > it may be that the broker is reporting its internal ip address to > > zookeeper which then may interfere with your ability to submit the the > > broker with a producer that isn't on AWS's network. you can make the > > broker report the public dns name instead of the internal host name > which i > > believe it reports by default. just update the host.name setting on the > > broker to the public dns address. hope this helps .. > > > > -Joe > > > > Sent from my Droid Charge on Verizon 4G LTE Jiang Jacky wrote: > > did anyone experience same issue? can you share with me? > > Thanks a lot. > > > > > > 2013/10/7 Jun Rao <jun...@gmail.com> > > > > > Kafka port is documented in > > > http://kafka.apache.org/documentation.html#brokerconfigs > > > > > > Thanks, > > > > > > Jun > > > > > > > > > On Sat, Oct 5, 2013 at 12:05 PM, Jiang Jacky <jiang0...@gmail.com> > > wrote: > > > > > > > Hi, I tried to setup the host.name in servier.properties, it doesn't > > > work. > > > > I believe it is the network security issue. However, I create a new > > > > instance in the same security group without kafka, zookeeper, it does > > > work, > > > > it can still produce to kafka server. but when I change to another > ec2 > > > > account, then create the same instance, and it cannot produce to > kafka > > > > server. > > > > I pay attention that there is no outbound port setting in the > security > > > > group configuration of kafka server ec2, I think if we shall have to > > set > > > > the outbound port for the firewall? > > > > Do you guys know which outbound port should be opened for kafka > server? > > > > Thanks > > > > > > > > > > > > 2013/10/5 Guozhang Wang <wangg...@gmail.com> > > > > > > > > > Hello Jacky, > > > > > > > > > > Have you read this FAQ: > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/FAQ#FAQ-OnEC2%2Cwhycan%27tmyhighlevelconsumersconnecttothebrokers%3F > > > > > > > > > > Guozhang > > > > > > > > > > > > > > > On Fri, Oct 4, 2013 at 10:41 PM, Jiang Jacky <jiang0...@gmail.com> > > > > wrote: > > > > > > > > > > > It is very weird, I have a kafka cluster in EC2, There is no any > > > > problem > > > > > to > > > > > > produce message from one of node by same producer. But when I > move > > > the > > > > > > producer to my local machine at home, then it gives me the below > > > error: > > > > > > Failed to send messages after 3 tries. > > > > > > > > > > > > Can anyone tell me how do I fix this issue? I have opened all > ports > > > of > > > > my > > > > > > machine at my home, and the security group is also opened for > kafka > > > > > server > > > > > > and zookeeper in EC2. Everything is fine, but I just cannot send > > any > > > > > > message to kafka server. > > > > > > Please help me. > > > > > > Thanks Everyone! > > > > > > > > > > > > Jacky > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > -- Guozhang > > > > > > > > > > > > > > >
