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:jun...@gmail.com]
Sent: Wednesday, July 31, 2013 10:57 AM
To: users@kafka.apache.org
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

<snandi...@verisign.com<mailto:snandi...@verisign.com>>wrote:



> Yes its Kafka 0.7.0 and my jars in core/lib  are

> metrics-core-3.0.0-c0c8be71.jar and metrics-annotation-3.0.0-c0c8be71.jar.

> I replaced them with metrics-core-2.2.0.jar metrics-annotation-2.2.0.jar.

>

> Please let me know how to replace without build errors..

>

> Thanks,

> Sujitha

>

> -----Original Message-----

> From: Jun Rao [mailto:jun...@gmail.com]

> Sent: Wednesday, July 31, 2013 12:19 AM

> To: users@kafka.apache.org<mailto:users@kafka.apache.org>

> Subject: Re: how to downgrade the metrics jar from 3.x to 2.2.0

>

> Hmm, are you sure this is Kafka 0.7? Kafka 0.7 doesn't use yammer

> metrics core. Only 0.8 does.

>

> Thanks,

>

> Jun

>

>

> On Tue, Jul 30, 2013 at 2:20 PM, Nandigam, Sujitha

> <snandi...@verisign.com<mailto:snandi...@verisign.com>>wrote:

>

> > Hi,

> >

> > I am running kafka-0.7 but when running producer got error

> > java.lang.NoSuchMethodError:

> com.yammer.metrics.core.TimerContext.stop()J.

> >

> > So I want to downgrade it to metrics 2.2.0 jar, So I replaced 3.x

> > jars with 2.2.0 jars then I am unable to build the jar file getting

> > below errors

> >

> > /kafka-0.7/core/src/main/scala/kafka/cluster/Partition.scala:64:

> > object creation impossible, since method value in class Gauge of

> > type ()Int is not defined

> > [error]     new Gauge[Int] {

> >

> > Please help regarding this...

> >

> > Thanks,

> > Sujitha

> > "This message (including any attachments) is intended only for the

> > use of the individual or entity to which it is addressed, and may

> > contain information that is non-public, proprietary, privileged,

> > confidential and exempt from disclosure under applicable law or may

> > be constituted as attorney work product. If you are not the intended

> > recipient, you are hereby notified that any use, dissemination,

> > distribution, or copying of this communication is strictly

> > prohibited. If you have received this message in error, notify

> > sender immediately and delete this message immediately."

> >

>

Reply via email to