You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by Jay Kreps <ja...@gmail.com> on 2014/03/18 15:36:21 UTC

Kafka-1310

This seems pretty serious, a single zookeeper go would take down all
connected brokers, no?
https://issues.apache.org/jira/browse/KAFKA-1310

-jay

Re: Kafka-1310

Posted by Neha Narkhede <ne...@gmail.com>.
The bug is not so much of "one zookeeper taking down all brokers" but more
of not being able to handle session expiration properly. This is definitely
a blocker.




On Tue, Mar 18, 2014 at 8:09 AM, Neha Narkhede <ne...@gmail.com>wrote:

> Well, depends. The behavior of zookeeper in a standalone dev mode and
> production "quorum" mode is pretty different. I'm taking a look at the JIRA
> to reproduce the issue.
>
> Thanks,
> Neha
>
>
> On Tue, Mar 18, 2014 at 7:36 AM, Jay Kreps <ja...@gmail.com> wrote:
>
>> This seems pretty serious, a single zookeeper go would take down all
>> connected brokers, no?
>> https://issues.apache.org/jira/browse/KAFKA-1310
>>
>> -jay
>>
>
>

Re: Kafka-1310

Posted by Neha Narkhede <ne...@gmail.com>.
Well, depends. The behavior of zookeeper in a standalone dev mode and
production "quorum" mode is pretty different. I'm taking a look at the JIRA
to reproduce the issue.

Thanks,
Neha


On Tue, Mar 18, 2014 at 7:36 AM, Jay Kreps <ja...@gmail.com> wrote:

> This seems pretty serious, a single zookeeper go would take down all
> connected brokers, no?
> https://issues.apache.org/jira/browse/KAFKA-1310
>
> -jay
>