[
https://issues.apache.org/jira/browse/KAFKA-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215160#comment-16215160
]
ASF GitHub Bot commented on KAFKA-6101:
---------------------------------------
GitHub user tedyu opened a pull request:
https://github.com/apache/kafka/pull/4118
KAFKA-6101 Reconnecting to broker does not exponentially backoff
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tedyu/kafka trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/4118.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4118
----
commit cd928d3867e42774bb167b3aaf11ca6a8dd8d48f
Author: tedyu <yuzhih...@gmail.com>
Date: 2017-10-23T13:49:27Z
KAFKA-6101 Reconnecting to broker does not exponentially backoff
----
> Reconnecting to broker does not exponentially backoff
> -----------------------------------------------------
>
> Key: KAFKA-6101
> URL: https://issues.apache.org/jira/browse/KAFKA-6101
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 0.11.0.0
> Reporter: Sean Rohead
> Attachments: 6101.v2.txt, 6101.v3.txt, text.html
>
>
> I am using com.typesafe.akka:akka-stream-kafka:0.17 which relies on
> kafka-clients:0.11.0.0.
> I have set the reconnect.backoff.max.ms property to 60000.
> When I start the application without kafka running, I see a flood of the
> following log message:
> [warn] o.a.k.c.NetworkClient - Connection to node -1 could not be
> established. Broker may not be available.
> The log messages occur several times a second and the frequency of these
> messages does not decrease over time as would be expected if exponential
> backoff was working properly.
> I set a breakpoint in the debugger in ClusterConnectionStates:188 and noticed
> that every time this breakpoint is hit, nodeState.failedAttempts is always 0.
> This is why the delay does not increase exponentially. It also appears that
> every time the breakpoint is hit, it is on a different instance, so even
> though the number of failedAttempts is incremented, we never get the
> breakpoint for the same instance more than one time.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
