[
https://issues.apache.org/jira/browse/KAFKA-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114569#comment-16114569
]
Jason Gustafson commented on KAFKA-5546:
----------------------------------------
If you bring the interface down, do open connections get closed cleanly? If
not, then the producer may be waiting for a request to timeout. You can
configure this with request.timeout.ms, which is 30s by default. It might also
help to look at the producer logs (at minimum debug level) to see if anything
else is going on.
> 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)
