under logs/. Thanks,
Jun On Thu, Oct 10, 2013 at 9:56 PM, Jiang Jacky <jiang0...@gmail.com> wrote: > Thanks Jun Rao > Where can I find those logs? > > > 2013/10/11 Jun Rao <jun...@gmail.com> > > > Any error in the controller and state-change log? > > > > Thanks, > > > > Jun > > > > > > On Thu, Oct 10, 2013 at 9:38 PM, Jiang Jacky <jiang0...@gmail.com> > wrote: > > > > > Hi, Aniket > > > Thanks for your reply > > > I checked the log from /tmp/kafka-logs/ > > > There are some empty files, likes 00000000000000000000.index, > > > 00000000000000000000.log. I cannot find any useful information there. > > > However, i found some other interesting things, I have posted here > > > > https://mail.google.com/mail/ca/u/0/#label/TechDiscuss/141a5c074641dd70 > > > Please have a look. Thanks a lot. > > > > > > > > > 2013/10/11 Aniket Bhatnagar <aniket.bhatna...@gmail.com> > > > > > > > Hi Jiang > > > > > > > > Just thinking out loud, it could be because Kafka can't connect to > > > > Zookeeper. Can you check Kafka logs to validate the same? > > > > > > > > > > > > On 11 October 2013 08:22, Jiang Jacky <jiang0...@gmail.com> wrote: > > > > > > > > > Hi, Everyone, I use the larger memory instance to replace that > small > > > one, > > > > > for now, I can create the topic, but when I try to produce message, > > it > > > > > still gives the same error. > > > > > Its so weird. can any one help me? Thanks > > > > > > > > > > > > > > > 2013/10/10 Jiang Jacky <jiang0...@gmail.com> > > > > > > > > > > > Another thing need is my instance comes with very small memory, > > just > > > > > 683M, > > > > > > I am not sure if it is related. I will try to use 8G memory > > instance. > > > > > > > > > > > > > > > > > > 2013/10/10 Jiang Jacky <jiang0...@gmail.com> > > > > > > > > > > > >> yes, even I cannot create new topic, same error, > > leadernotavailable. > > > > > >> My zookeeper and storm all are working very well, except of > Kafka. > > > > > >> > > > > > >> > > > > > >> 2013/10/10 Neha Narkhede <neha.narkh...@gmail.com> > > > > > >> > > > > > >>> Are you trying to produce these messages to a newly created > > topic? > > > > > >>> > > > > > >>> > > > > > >>> On Thu, Oct 10, 2013 at 6:15 PM, Jiang Jacky < > > jiang0...@gmail.com> > > > > > >>> wrote: > > > > > >>> > > > > > >>> > can anyone help me? Thanks a lot > > > > > >>> > > > > > > >>> > > > > > > >>> > 2013/10/10 Jiang Jacky <jiang0...@gmail.com> > > > > > >>> > > > > > > >>> > > Hi, I run into kafka issue recently, when I try to produce > a > > > > > >>> message, it > > > > > >>> > > gives me follow error > > > > > >>> > > > > > > > >>> > > [2013-10-11 00:30:26,740] INFO Fetching metadata from > broker > > > > > >>> > > id:0,host:localhost,port:9092 with correlation id 47 for 1 > > > > topic(s) > > > > > >>> > > Set(my-replicated-topic) (kafka.client.ClientUtils$) > > > > > >>> > > [2013-10-11 00:30:26,741] INFO Connected to localhost:9092 > > for > > > > > >>> producing > > > > > >>> > > (kafka.producer.SyncProducer) > > > > > >>> > > [2013-10-11 00:30:26,753] INFO Disconnecting from > > > localhost:9092 > > > > > >>> > > (kafka.producer.SyncProducer) > > > > > >>> > > [2013-10-11 00:30:26,753] INFO Closing socket connection > to / > > > > > >>> 127.0.0.1. > > > > > >>> > > (kafka.network.Processor) > > > > > >>> > > [2013-10-11 00:30:26,754] WARN Error while fetching > metadata > > > > > >>> > > [{TopicMetadata for topic my-replicated-topic -> > > > > > >>> > > No partition metadata for topic my-replicated-topic due to > > > > > >>> > > kafka.common.LeaderNotAvailableException}] for topic > > > > > >>> > [my-replicated-topic]: > > > > > >>> > > class kafka.common.LeaderNotAvailableException > > > > > >>> > > (kafka.producer.BrokerPartitionInfo) > > > > > >>> > > [2013-10-11 00:30:26,755] ERROR Failed to collate messages > by > > > > > topic, > > > > > >>> > > partition due to: Failed to fetch topic metadata for topic: > > > > > >>> > > my-replicated-topic > > (kafka.producer.async.DefaultEventHandler) > > > > > >>> > > [2013-10-11 00:30:26,755] INFO Back off for 100 ms before > > > > retrying > > > > > >>> send. > > > > > >>> > > Remaining retries = 0 > > > (kafka.producer.async.DefaultEventHandler) > > > > > >>> > > [2013-10-11 00:30:26,856] INFO Fetching metadata from > broker > > > > > >>> > > id:0,host:localhost,port:9092 with correlation id 48 for 1 > > > > topic(s) > > > > > >>> > > Set(my-replicated-topic) (kafka.client.ClientUtils$) > > > > > >>> > > [2013-10-11 00:30:26,857] INFO Connected to localhost:9092 > > for > > > > > >>> producing > > > > > >>> > > (kafka.producer.SyncProducer) > > > > > >>> > > [2013-10-11 00:30:26,874] INFO Disconnecting from > > > localhost:9092 > > > > > >>> > > (kafka.producer.SyncProducer) > > > > > >>> > > [2013-10-11 00:30:26,874] INFO Closing socket connection > to / > > > > > >>> 127.0.0.1. > > > > > >>> > > (kafka.network.Processor) > > > > > >>> > > [2013-10-11 00:30:26,875] WARN Error while fetching > metadata > > > > > >>> > > [{TopicMetadata for topic my-replicated-topic -> > > > > > >>> > > No partition metadata for topic my-replicated-topic due to > > > > > >>> > > kafka.common.LeaderNotAvailableException}] for topic > > > > > >>> > [my-replicated-topic]: > > > > > >>> > > class kafka.common.LeaderNotAvailableException > > > > > >>> > > (kafka.producer.BrokerPartitionInfo) > > > > > >>> > > [2013-10-11 00:30:26,876] ERROR Failed to send requests for > > > > topics > > > > > >>> > > my-replicated-topic with correlation ids in [41,48] > > > > > >>> > > (kafka.producer.async.DefaultEventHandler) > > > > > >>> > > [2013-10-11 00:30:26,876] ERROR Error in handling batch of > 1 > > > > events > > > > > >>> > > (kafka.producer.async.ProducerSendThread) > > > > > >>> > > kafka.common.FailedToSendMessageException: Failed to send > > > > messages > > > > > >>> after > > > > > >>> > 3 > > > > > >>> > > tries. > > > > > >>> > > at > > > > > >>> > > > > > > > >>> > > > > > > >>> > > > > > > > > > > > > > > > kafka.producer.async.DefaultEventHandler.handle(DefaultEventHandler.scala:90) > > > > > >>> > > at > > > > > >>> > > > > > > > >>> > > > > > > >>> > > > > > > > > > > > > > > > kafka.producer.async.ProducerSendThread.tryToHandle(ProducerSendThread.scala:104) > > > > > >>> > > at > > > > > >>> > > > > > > > >>> > > > > > > >>> > > > > > > > > > > > > > > > kafka.producer.async.ProducerSendThread$$anonfun$processEvents$3.apply(ProducerSendThread.scala:87) > > > > > >>> > > at > > > > > >>> > > > > > > > >>> > > > > > > >>> > > > > > > > > > > > > > > > kafka.producer.async.ProducerSendThread$$anonfun$processEvents$3.apply(ProducerSendThread.scala:67) > > > > > >>> > > at > > > > > >>> scala.collection.immutable.Stream.foreach(Stream.scala:254) > > > > > >>> > > at > > > > > >>> > > > > > > > >>> > > > > > > >>> > > > > > > > > > > > > > > > kafka.producer.async.ProducerSendThread.processEvents(ProducerSendThread.scala:66) > > > > > >>> > > at > > > > > >>> > > > > > > > >>> > > > > > > > > > kafka.producer.async.ProducerSendThread.run(ProducerSendThread.scala:44) > > > > > >>> > > > > > > > >>> > > > > > > > >>> > > I have no idea why the leader is not available.Can someone > > give > > > > me > > > > > a > > > > > >>> > hint? > > > > > >>> > > Thanks a lot. > > > > > >>> > > > > > > > >>> > > > > > > >>> > > > > > >> > > > > > >> > > > > > > > > > > > > > > > > > > > > >
