[
https://issues.apache.org/jira/browse/KAFKA-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083991#comment-16083991
]
M. Manna edited comment on KAFKA-5585 at 7/12/17 2:05 PM:
----------------------------------------------------------
Jinx or not, I was doing some PoC test on reliability on Windows. Somewhat
similar issues to what's been reported here (i guess however, my linger.ms and
backoff.ms need to be adjusted properly)
Two topics *z1* (partitions 1 repfactor 3) and *z3* (partitions 3 repfactor 3)
should be created beforehand. Attached files are
1) Source code for my stress testing - Need to create a project with *Log4j *-
test_project_files.zip
2) Test results excel sheet - Stress Test Windows
3) Cluster properties file - broker_zookeeper_configs.zip
was (Author: manme...@gmail.com):
Jinx or not, I was doing some PoC test on reliability on Windows. Somewhat
similar issues to what's been reported here (i guess however, my linger.ms and
backoff.ms need to be adjusted properly)
Two topics *z1* (partitions 1 repfactor 3) and *z3* (partitions 3 repfactor 3)
should be created beforehand. Attached files are
1) Source code for my stress testing - Need to create a project with *Log4j *-
test_project_files.zip
2) Test results excel sheet - Stress Test Windows
> 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
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
