Philip OToole 2013-08-23, 15:15
Bo Sun 2013-01-17, 06:10
Jun Rao 2013-01-17, 15:26
Bo Sun 2013-01-21, 02:23
When the consumption stops in GroupA, were there any error/exception in the
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.
On Sun, Jan 20, 2013 at 6:22 PM, Bo Sun <[EMAIL PROTECTED]> wrote:
> 0.7.1 thanks
> On Thu, Jan 17, 2013 at 11:26 PM, Jun Rao <[EMAIL PROTECTED]> wrote:
> > What version of Kafka are you using?
> > Thanks,
> > Jun
> > On Wed, Jan 16, 2013 at 10:10 PM, Bo Sun <[EMAIL PROTECTED]> 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
> > in
> > > this new consumer , i got the new data. and i get the new data from
> > > old consumer.(groupA) at the same time.
> > > i don't know what's wrong with it.
> > > did i do the wrong things ?
> > > thanks
> > >
Bo Sun 2013-01-21, 10:56
Jun Rao 2013-01-21, 16:09
Bo Sun 2013-01-22, 02:22