Thanks, Neha. We are planning to migrate to 0.8.1.

Regards,

Libo


-----Original Message-----
From: Neha Narkhede [mailto:[email protected]] 
Sent: Friday, February 07, 2014 10:26 AM
To: [email protected]
Subject: RE: Consumer's behavior when brokers are temporarily not available.

Yes bouncing the process will allow you to consume again. Also would you mind 
giving 0.8 final a try? It is much more stable compared to 0.8 beta.

Thanks,
Neha
On Feb 7, 2014 6:49 AM, "Yu, Libo" <[email protected]> wrote:

> We are using 0.8 beta1. Our zookeeper had some issue which in turn 
> triggered consumer rebalance.
> In this case, after maximum number of retries, the rebalance failed, 
> should we bounce our process in order to consume again?
>
> Regards,
>
> Libo
>
>
> -----Original Message-----
> From: Jun Rao [mailto:[email protected]]
> Sent: Friday, February 07, 2014 12:03 AM
> To: [email protected]
> Subject: Re: Consumer's behavior when brokers are temporarily not 
> available.
>
> Which version are you using? In 0.8, broker failure won't trigger 
> consumer rebalances. Only changes in #partitions and consumers will 
> trigger rebalances.
>
> Thanks,
>
> Jun
>
>
> On Thu, Feb 6, 2014 at 10:46 AM, Yu, Libo <[email protected]> wrote:
>
> > While the broker is not available (caused by zookeeper issue), the 
> > rebalance will fail. Should rebalance succeed in this case? Thanks.
> >
> >
> > Regards,
> >
> > Libo
> >
> >
> > -----Original Message-----
> > From: Guozhang Wang [mailto:[email protected]]
> > Sent: Thursday, February 06, 2014 12:49 PM
> > To: [email protected]
> > Subject: Re: Consumer's behavior when brokers are temporarily not 
> > available.
> >
> > Neha is right, though it is a little interesting that consumers did 
> > not achieve a concensus after four retries have exhasuted, for just 
> > an event of broker-failure.
> >
> > Could you check your consumer log searching for "begin rebalance" 
> > and check what caused these rebalances to fail?
> >
> > Guozhang
> >
> >
> > On Thu, Feb 6, 2014 at 9:12 AM, Neha Narkhede 
> > <[email protected]
> > >wrote:
> >
> > > The consumer only retries "rebalance.max.retries" times. Once it 
> > > runs out of the retries, it needs to be restarted to consume again.
> > >
> > >
> > >
> > >
> > > On Thu, Feb 6, 2014 at 9:05 AM, Yu, Libo <[email protected]> wrote:
> > >
> > > > Hi folks,
> > > >
> > > > This is what we experienced recently:
> > > > Some zookeeper's issue made broker unavailable for a short 
> > > > period of
> > > time.
> > > > On the consumer side, this triggered rebalance and rebalanced 
> > > > failed
> > > after
> > > > four tries.
> > > > So while should we expect while the broker is not up? Should 
> > > > consumer
> > > keep
> > > > trying to rebalance or wait for the brokers to be brought back?
> >  Thanks.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Libo
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > -- Guozhang
> >
>

Reply via email to