kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Bayer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5585) Failover in a replicated Cluster does not work
Date Wed, 12 Jul 2017 12:25:00 GMT

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

Thomas Bayer updated KAFKA-5585:
--------------------------------
    Description: 
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 Config:
{{props.put(BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
props.put(ACKS_CONFIG, "all");
props.put(BUFFER_MEMORY_CONFIG, 33554432);}}

Consumer Config:
{{ props.put(BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
props.put(GROUP_ID_CONFIG, "a");
props.put(ENABLE_AUTO_COMMIT_CONFIG, "true");
props.put(AUTO_COMMIT_INTERVAL_MS_CONFIG, "1000");
props.put(SESSION_TIMEOUT_MS_CONFIG, "30000");}}

  was:
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.


> 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
>
> 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 Config:
> {{props.put(BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
> props.put(ACKS_CONFIG, "all");
> props.put(BUFFER_MEMORY_CONFIG, 33554432);}}
> Consumer Config:
> {{ props.put(BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
> props.put(GROUP_ID_CONFIG, "a");
> props.put(ENABLE_AUTO_COMMIT_CONFIG, "true");
> props.put(AUTO_COMMIT_INTERVAL_MS_CONFIG, "1000");
> props.put(SESSION_TIMEOUT_MS_CONFIG, "30000");}}



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

Mime
View raw message