Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> Re: class kafka.common.LeaderNotAvailableException (kafka.producer.BrokerPartitionInfo)


Copy link to this message
-
Re: class kafka.common.LeaderNotAvailableException (kafka.producer.BrokerPartitionInfo)
It seems that you have only one replica on broker 2 for that partition and
that broker is down. That's why that partition is not available.

Thanks,

Jun
On Thu, Aug 1, 2013 at 6:33 AM, Nandigam, Sujitha <[EMAIL PROTECTED]>wrote:

> Yes, below is the exception I see in state-change log..
>
> ERROR Controller 1 epoch 1 initiated state change for partition
> [VeriSign.all.dns.hydra,0] from OfflinePartition to OnlinePartition failed
> (state.change.logger)
> kafka.common.NoReplicaOnlineException: No replica for partition
> [VeriSign.all.dns.hydra,0] is alive. Live brokers are: [Set(1)], Assigned
> replicas are: [List(2)]
>
>
> -----Original Message-----
> From: Jun Rao [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 01, 2013 12:53 AM
> To: [EMAIL PROTECTED]
> Subject: Re: class kafka.common.LeaderNotAvailableException
> (kafka.producer.BrokerPartitionInfo)
>
> Any error in the broker's state-change log?
>
> Thanks,
>
> Jun
>
>
> On Wed, Jul 31, 2013 at 2:32 PM, Nandigam, Sujitha
> <[EMAIL PROTECTED]>wrote:
>
> > I am running 0.8 beta version, I wrote a producer with
> > auto.create.topics.enable = true & type async , When I run the
> > producer class  getting below
> >
> > [ProducerSendThread-] INFO Fetching metadata from broker
> > id:0,host:localhost,port:9093 with correlation id 0 for 6 topic(s)
> >
> >
> >
> > INFO Fetching metadata from broker id:1,host:localhost,port:9094 with
> > correlation id 2 for 6 topic(s) Set
> >
> >
> >
> > But I have boker. id =1 for 9093 and boker. id =2 for 9094
> >
> >
> >
> > Also below exceptions
> >
> >
> >
> > [2013-07-31 21:15:49,861] [ProducerSendThread-] DEBUG Handling 6
> > events
> > (kafka.producer.async.DefaultEventHandler)
> >
> > [2013-07-31 21:15:49,958] [ProducerSendThread-] INFO Fetching metadata
> > from broker id:0,host:localhost,port:9093 with correlation id 0 for 6
> > topic(s) Set(VeriSign.recdns.RECCNM2-IAD3.dns.hydra,
> > VeriSign.all.dns.hydra, VeriSign.recdns.IAD3.dns.hydra,
> > VeriSign.IAD3.dns.hydra, VeriSign.recdns.dns.hydra,
> > VeriSign.RECCNM2-IAD3.dns.hydra) (kafka.client.ClientUtils$)
> >
> > [2013-07-31 21:15:49,966] [ProducerSendThread-] DEBUG Created socket
> > with SO_TIMEOUT = 10000 (requested 10000), SO_RCVBUF = 43690
> > (requested -1), SO_SNDBUF = 102400 (requested 102400).
> > (kafka.network.BlockingChannel)
> >
> > [2013-07-31 21:15:49,966] [ProducerSendThread-] INFO Connected to
> > localhost:9093 for producing (kafka.producer.SyncProducer)
> >
> > [2013-07-31 21:15:50,122] [ProducerSendThread-] INFO Disconnecting
> > from
> > localhost:9093 (kafka.producer.SyncProducer)
> >
> > [2013-07-31 21:15:50,125] [ProducerSendThread-] DEBUG Successfully
> > fetched metadata for 6 topic(s)
> > Set(VeriSign.recdns.RECCNM2-IAD3.dns.hydra,
> > VeriSign.all.dns.hydra, VeriSign.recdns.IAD3.dns.hydra,
> > VeriSign.IAD3.dns.hydra, VeriSign.recdns.dns.hydra,
> > VeriSign.RECCNM2-IAD3.dns.hydra) (kafka.client.ClientUtils$)
> >
> > [2013-07-31 21:15:50,144] [ProducerSendThread-] WARN Error while
> > fetching metadata [{TopicMetadata for topic
> > VeriSign.recdns.IAD3.dns.hydra ->
> >
> > No partition metadata for topic VeriSign.recdns.IAD3.dns.hydra due to
> > kafka.common.LeaderNotAvailableException}] for topic
> > [VeriSign.recdns.IAD3.dns.hydra]: class
> > kafka.common.LeaderNotAvailableException
> >  (kafka.producer.BrokerPartitionInfo)
> >
> >
> >
> > Please have a look and let me know my mistake.
> >
> >
> >
> > Thanks,
> >
> > Sujitha
> >
> >
> >
> > -----Original Message-----
> > From: Jun Rao [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, July 31, 2013 10:57 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: how to downgrade the metrics jar from 3.x to 2.2.0
> >
> >
> >
> > From the code path, this is clearly 0.8 code. How did you get the
> > Kafka jar? Also, Kafka 0.8 only works with metrics 2.2.0.
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Jun
> >
> >
> >
> >
> >
> > On Wed, Jul 31, 2013 at 6:52 AM, Nandigam, Sujitha
> >
> > <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>wrote:

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB