You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Björn Eriksson (JIRA)" <ji...@apache.org> on 2017/06/30 13:37:00 UTC
[jira] [Created] (KAFKA-5546) Lost data when the leader is
disconnected.
Björn Eriksson created KAFKA-5546:
-------------------------------------
Summary: Lost data when the leader is disconnected.
Key: KAFKA-5546
URL: https://issues.apache.org/jira/browse/KAFKA-5546
Project: Kafka
Issue Type: Bug
Components: producer
Affects Versions: 0.10.2.1
Reporter: Björn Eriksson
Attachments: kafka-failure-log.txt
We've noticed that if the leaders networking is deconfigured (with {{ifconfig eth0 down}}) the producer won't notice this and doesn't immediately connect to the newly elected leader.
{{docker-compose.yml}} and test runner are at https://github.com/owbear/kafka-network-failure-tests with sample test output at https://github.com/owbear/kafka-network-failure-tests/blob/master/README.md#sample-results
I was expecting a transparent failover to the new leader.
The attached log shows that while the producer produced values between {{12:37:33}} and {{12:37:54}}, theres a gap between {{12:37:41}} and {{12:37:50}} where no values was stored in the log after the network was taken down at {{12:37:42}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)