[ 
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 and consumer config: see attached files


*Log Consumer:*
{{2017-07-12 16:15:26 WARN  ConsumerCoordinator:649 - Auto-commit of offsets 
{produktion-0=OffsetAndMetadata{offset=10, metadata=''}} failed for group a: 
Offset commit failed with a retriable exception. You should retry committing 
offsets. The underlying error was: The coordinator is not available.
2017-07-12 16:15:26 WARN  NetworkClient:588 - Connection to node 2147483645 
could not be established. Broker may not be available.
2017-07-12 16:15:26 WARN  NetworkClient:588 - Connection to node 2 could not be 
established. Broker may not be available.}}

*Log Producer:*
{{2017-07-12 16:15:32 WARN  NetworkClient:588 - Connection to node -1 could not 
be established. Broker may not be available.}}



  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.

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




> 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: broker_zookeeper_configs.zip, 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
> *Log Consumer:*
> {{2017-07-12 16:15:26 WARN  ConsumerCoordinator:649 - Auto-commit of offsets 
> {produktion-0=OffsetAndMetadata{offset=10, metadata=''}} failed for group a: 
> Offset commit failed with a retriable exception. You should retry committing 
> offsets. The underlying error was: The coordinator is not available.
> 2017-07-12 16:15:26 WARN  NetworkClient:588 - Connection to node 2147483645 
> could not be established. Broker may not be available.
> 2017-07-12 16:15:26 WARN  NetworkClient:588 - Connection to node 2 could not 
> be established. Broker may not be available.}}
> *Log Producer:*
> {{2017-07-12 16:15:32 WARN  NetworkClient:588 - Connection to node -1 could 
> not be established. Broker may not be available.}}



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

Reply via email to