0.8.0 should be the most stable version. Also, try starting with a new consumer group and see if this works. The old group may already have offsets committed to ZK.
Thanks, Jun On Thu, Jan 16, 2014 at 7:57 AM, Hussain Pirosha < hussain.piro...@impetus.co.in> wrote: > Hi Jun, > > I tried that too but it didn't worked. What version of kafka is currently > best suitable for production ? > > Thanks, > Hussain > > -----Original Message----- > From: Jun Rao [mailto:jun...@gmail.com] > Sent: Thursday, January 16, 2014 9:24 PM > To: users@kafka.apache.org > Subject: Re: High level consumer does not consumes in 0.8.0 version > > By default, a new consumer consumes from the end of the queue, ie. only > newly produced messages will be consumed. Try producing some more messages > after the consumer is up or setting the consumer property to consume from > the beginning. You shouldn't need to commit offset on every message, which > is inefficient on ZK. > > Thanks, > > Jun > > > On Thu, Jan 16, 2014 at 7:14 AM, Hussain Pirosha < > hussain.piro...@impetus.co.in> wrote: > > > Hello, > > > > While running the high level consumer mentioned on > > > https://cwiki.apache.org/confluence/display/KAFKA/Consumer+Group+Exampleusing0.8.0 > release. > > The consumer does not receive any messages and blocks on > > stream.hasNext() call. I have pasted the client side logs at > > https://gist.github.com/hpirosha/8456360. > > > > The same thing works if I use the code from > > kafka.consumer.ConsoleConsumer. Difference between them is using the > > ConsumerConnector#createMessageStreamsByFilter while the high level > > consumer invokes the ConsumerConnector#createMessageStreams api. Has > > the former api got broken or the wiki is not up-to-date ? > > > > Pardon me if this has been already discussed in the group. > > > > Thanks, > > Hussain > > > > ________________________________ > > > > > > > > > > > > > > NOTE: This message may contain information that is confidential, > > proprietary, privileged or otherwise protected by law. The message is > > intended solely for the named addressee. If received in error, please > > destroy and notify the sender. Any use of this email is prohibited > > when received in error. Impetus does not represent, warrant and/or > > guarantee, that the integrity of this communication has been > > maintained nor that the communication is free of errors, virus, > interception or interference. > > > > ________________________________ > > > > > > > NOTE: This message may contain information that is confidential, > proprietary, privileged or otherwise protected by law. The message is > intended solely for the named addressee. If received in error, please > destroy and notify the sender. Any use of this email is prohibited when > received in error. Impetus does not represent, warrant and/or guarantee, > that the integrity of this communication has been maintained nor that the > communication is free of errors, virus, interception or interference. >
