kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-6101) Reconnecting to broker does not exponentially backoff
Date Mon, 23 Oct 2017 15:36:01 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ismael Juma resolved KAFKA-6101.
    Resolution: Fixed
      Assignee: Ted Yu

> 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:
>            Reporter: Sean Rohead
>            Assignee: Ted Yu
>             Fix For: 1.0.0, 1.1.0
>         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:
> 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
> [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

View raw message