You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by "Yu, Libo " <li...@citi.com> on 2014/02/14 21:15:29 UTC

broker offline

Hi team,

We have three brokers on our production cluster. I noticed two of them somehow
got offline and then re-registered with zookeeper and got back online. It seems the
issue was caused by some zookeeper issue. So I want to know what may be the possible
cases of the issue. If I want to reproduce the issue, is there any way to do it? Thanks.

Regards,

Libo


Re: broker offline

Posted by Guozhang Wang <wa...@gmail.com>.
Yes, it will be queued, and the second rebalance will start right after the
first one.


On Fri, Feb 21, 2014 at 8:50 AM, Yu, Libo <li...@citi.com> wrote:

> In our case, two brokers were offline. When the first broker was offline,
> that would trigger a rebalance. When the second broker was offline, if the
> consumers were in the process of rebalance, what do we expect? Is the
> second rebalance request queued?
>
> Regards,
>
> Libo
>
>
> -----Original Message-----
> From: Guozhang Wang [mailto:wangguoz@gmail.com]
> Sent: Friday, February 14, 2014 7:33 PM
> To: users@kafka.apache.org
> Subject: Re: broker offline
>
> Hello Libo,
>
> When ZK resumes from a soft failure, like a GC, it will mark the ephemeral
> nodes as session timed out, and the brokers will try to re-register upon
> receiving the session timeout. You can re-produce this issue by signal
> pause the ZK process.
>
> Guozhang
>
>
> On Fri, Feb 14, 2014 at 12:15 PM, Yu, Libo <li...@citi.com> wrote:
>
> > Hi team,
> >
> > We have three brokers on our production cluster. I noticed two of them
> > somehow got offline and then re-registered with zookeeper and got back
> > online. It seems the issue was caused by some zookeeper issue. So I
> > want to know what may be the possible cases of the issue. If I want to
> > reproduce the issue, is there any way to do it? Thanks.
> >
> > Regards,
> >
> > Libo
> >
> >
>
>
> --
> -- Guozhang
>



-- 
-- Guozhang

RE: broker offline

Posted by "Yu, Libo " <li...@citi.com>.
In our case, two brokers were offline. When the first broker was offline,
that would trigger a rebalance. When the second broker was offline, if the 
consumers were in the process of rebalance, what do we expect? Is the 
second rebalance request queued? 

Regards,

Libo


-----Original Message-----
From: Guozhang Wang [mailto:wangguoz@gmail.com] 
Sent: Friday, February 14, 2014 7:33 PM
To: users@kafka.apache.org
Subject: Re: broker offline

Hello Libo,

When ZK resumes from a soft failure, like a GC, it will mark the ephemeral nodes as session timed out, and the brokers will try to re-register upon receiving the session timeout. You can re-produce this issue by signal pause the ZK process.

Guozhang


On Fri, Feb 14, 2014 at 12:15 PM, Yu, Libo <li...@citi.com> wrote:

> Hi team,
>
> We have three brokers on our production cluster. I noticed two of them 
> somehow got offline and then re-registered with zookeeper and got back 
> online. It seems the issue was caused by some zookeeper issue. So I 
> want to know what may be the possible cases of the issue. If I want to 
> reproduce the issue, is there any way to do it? Thanks.
>
> Regards,
>
> Libo
>
>


--
-- Guozhang

Re: broker offline

Posted by Guozhang Wang <wa...@gmail.com>.
Hello Libo,

When ZK resumes from a soft failure, like a GC, it will mark the ephemeral
nodes as session timed out, and the brokers will try to re-register upon
receiving the session timeout. You can re-produce this issue by signal
pause the ZK process.

Guozhang


On Fri, Feb 14, 2014 at 12:15 PM, Yu, Libo <li...@citi.com> wrote:

> Hi team,
>
> We have three brokers on our production cluster. I noticed two of them
> somehow
> got offline and then re-registered with zookeeper and got back online. It
> seems the
> issue was caused by some zookeeper issue. So I want to know what may be
> the possible
> cases of the issue. If I want to reproduce the issue, is there any way to
> do it? Thanks.
>
> Regards,
>
> Libo
>
>


-- 
-- Guozhang