You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "M. Manna (JIRA)" <ji...@apache.org> on 2017/07/12 13:44:00 UTC

[jira] [Issue Comment Deleted] (KAFKA-5585) Failover in a replicated Cluster does not work

     [ https://issues.apache.org/jira/browse/KAFKA-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

M. Manna updated KAFKA-5585:
----------------------------
    Comment: was deleted

(was: Need to create a project with log4j dependency)

> Failover in a replicated Cluster does not work
> ----------------------------------------------
>
>                 Key: KAFKA-5585
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5585
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.11.0.0
>         Environment: Linux, Mac OSX
>            Reporter: Thomas Bayer
>         Attachments: SimpleConsumer.java, SimpleProducer.java, Stress Test Windows.xlsx, test_project_files.zip
>
>
> Failover does not work in a cluster with 3 nodes and a replicated topic with factor 3.
> You can reproduce it als follows: Setup 3 Kafka Nodes and 1 Zookeeper. Than create a topic with factor 3. Start a consumer. Stop a node. Write to the topic. Now you get warnings that the client can not connect to a broker. The consumer does not receive any messages.
> The same setup works like a charm with 0.10.2.1.
> Broker Config:
> {{broker.id=1
> listeners=PLAINTEXT://:9091
> log.dirs=cluster/logs/node-1
> broker.id=2
> listeners=PLAINTEXT://:9092
> log.dirs=cluster/logs/node-2
> broker.id=3
> listeners=PLAINTEXT://:9093
> log.dirs=cluster/logs/node-3}}
> Rest of the config is from the distribution.
> Producer and consumer config: see attached files



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)