[
https://issues.apache.org/jira/browse/KAFKA-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128785#comment-16128785
]
Ismael Juma commented on KAFKA-5546:
------------------------------------
What guarantees are you aiming for? You can tweak timeouts like the producer's
request.timeout.ms and the broker's zookeeper.session.timeout.ms so that such
issues are detected quicker. If your network is unreliable (like AWS, for
example), then this is likely to have undesired effects, however.
> Temporary loss of availability 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, 0.11.0.0
> Environment: docker, failing-network
> Reporter: Björn Eriksson
>
> 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.
> We were expecting a transparent failover to the new leader but testing shows
> that there's a 8-15 seconds long gap where no values are stored in the log
> after the network is taken down.
> Tests (and results) [against
> 0.10.2.1|https://github.com/owbear/kafka-network-failure-tests/tree/kafka-network-failure-tests-0.10.2.1]
> Tests (and results) [against
> 0.11.0.0|https://github.com/owbear/kafka-network-failure-tests/tree/kafka-network-failure-tests-0.11.0.0]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
