Normally it shouldn't. If the problem shows up again, I suggest that you use the ConsumerOffsetChecker tool to see if the consumer is indeed lagging.
Thanks, Jun On Mon, Jan 21, 2013 at 2:56 AM, Bo Sun <docsun...@gmail.com> wrote: > it's not any exceptions. i found sth.today, "several days later " , it's > no data to produce to kafka. but after several days . kafka get the new > data. but cannot consume anything . is that ( no data days ) couse the > problem? > > Thanks Eric > > On Mon, Jan 21, 2013 at 2:13 PM, Jun Rao <jun...@gmail.com> wrote: > > > When the consumption stops in GroupA, were there any error/exception in > the > > consumer logic? > > > > One common cause for a consumer to stop is that the application code hits > > an exception while consuming an event. In particular, if you are using > java > > thread pool and haven't attached an exception handler, those exceptions > > will be eaten and you won't see them in the application log. The solution > > is to add a try/catch clause in the application code to log all > Throwables. > > > > Thanks, > > > > Jun > > > > > > On Sun, Jan 20, 2013 at 6:22 PM, Bo Sun <docsun...@gmail.com> wrote: > > > > > 0.7.1 thanks > > > > > > On Thu, Jan 17, 2013 at 11:26 PM, Jun Rao <jun...@gmail.com> wrote: > > > > > > > What version of Kafka are you using? > > > > > > > > Thanks, > > > > > > > > Jun > > > > > > > > On Wed, Jan 16, 2013 at 10:10 PM, Bo Sun <docsun...@gmail.com> > wrote: > > > > > > > > > I'v got a problem like this. > > > > > 1. I use the groupname "GourpA" to consume the kafka topic > "topicA" . > > > > > several days later , we cannot got the new data from the consumer. > > > > > 2. Then i use the groupname "groupB" to consume the kafa topic > > > "topicA". > > > > in > > > > > this new consumer , i got the new data. and i get the new data > from > > > the > > > > > old consumer.(groupA) at the same time. > > > > > i don't know what's wrong with it. > > > > > did i do the wrong things ? > > > > > thanks > > > > > > > > > > > > > > >
