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 >> 0.8.0 producer can't connect to cluster?


Copy link to this message
-
Re: 0.8.0 producer can't connect to cluster?
I will submit the issue about debug.

How can I get the updated yammer jar? Or do I need to wait for an official
release distribution (vs pulling from svn)?

Thanks,

Chris
On Tue, Nov 27, 2012 at 1:17 PM, Jay Kreps <[EMAIL PROTECTED]> wrote:

> Yes, we had to patch metrics due to a bug. The patched jar is shipped with
> the distribution until they get a release out.
>
> But logging this in debug is a bug. Would you be willing to file a ticket
> for this?
>
> Thanks!
>
> -jay
>
>
> On Tue, Nov 27, 2012 at 10:12 AM, Chris Curtin <[EMAIL PROTECTED]
> >wrote:
>
> > Okay, figured out that you need to turn on Log4j logger to DEBUG then you
> > get a NoSuchMethodError around yammer. (see below)
> >
> > I'm running yammer 2.2.0 since that seems to be all I can find via maven.
> > Is there a different version needed?
> >
> > Thanks,
> >
> > Chris
> >
> > 257  [main] INFO  kafka.producer.SyncProducer  - Connected to
> > 10.121.31.55:9094 for producing
> > 286  [main] WARN  kafka.producer.async.DefaultEventHandler  - failed to
> > send to broker 3 with data Map([test1,0] ->
> > ByteBufferMessageSet(MessageAndOffset(Message(magic = 2, attributes = 0,
> > crc = 1906312613, key = null, payload = java.nio.HeapByteBuffer[pos=0
> > lim=22 cap=22]),0), ))
> > java.lang.NoSuchMethodError: com.yammer.metrics.core.TimerContext.stop()J
> > at kafka.metrics.KafkaTimer.time(KafkaTimer.scala:36)
> > at kafka.producer.SyncProducer.send(SyncProducer.scala:94)
> > at
> >
> >
> kafka.producer.async.DefaultEventHandler.kafka$producer$async$DefaultEventHandler$$send(DefaultEventHandler.scala:221)
> > at
> >
> >
> kafka.producer.async.DefaultEventHandler$$anonfun$dispatchSerializedData$1.apply(DefaultEventHandler.scala:87)
> > at
> >
> >
> kafka.producer.async.DefaultEventHandler$$anonfun$dispatchSerializedData$1.apply(DefaultEventHandler.scala:81)
> > at
> >
> scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80)
> > at
> >
> scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:80)
> > at scala.collection.Iterator$class.foreach(Iterator.scala:631)
> > at
> scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:161)
> > at
> >
> scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:194)
> > at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:39)
> > at scala.collection.mutable.HashMap.foreach(HashMap.scala:80)
> > at
> >
> >
> kafka.producer.async.DefaultEventHandler.dispatchSerializedData(DefaultEventHandler.scala:81)
> > at
> >
> >
> kafka.producer.async.DefaultEventHandler.handle(DefaultEventHandler.scala:57)
> > at kafka.producer.Producer.send(Producer.scala:75)
> > at kafka.javaapi.producer.Producer.send(Producer.scala:32)
> > at
> com.silverpop.kafka.playproducer.TestProducer.main(TestProducer.java:40)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > at
> >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:597)
> > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
> >
> >
> > On Tue, Nov 27, 2012 at 12:30 PM, Jun Rao <[EMAIL PROTECTED]> wrote:
> >
> > > When the producer fails to send in 3 retries, it will log an error.
> > Before
> > > that, in the producer, we log the failure of each of the retries in
> warn
> > > and it tells you the cause.
> > >
> > > Also, did you create the topic first?
> > >
> > > Thanks,
> > >
> > > Jun
> > >
> > > On Tue, Nov 27, 2012 at 8:56 AM, Chris Curtin <[EMAIL PROTECTED]
> > > >wrote:
> > >
> > > > The error from when it fails is all I get. Nothing on the broker side
> > and
> > > > no other errors or exceptions on the client.
> > > >
> > > > Where should I be looking for the reasons? Is there a callback I
> should
> > > be
> > > > implementing?
> > > >
> > > > Thanks,
> > > >
> > > > Chris
> > > >
> > > >
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