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 >
