Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@kafka.apache.org
Date: Fri, 20 Oct 2017 22:56:00 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: jira@kafka.apache.org
Message-ID: <JIRA.13111087.1508530316000.22597.1508540160363@Atlassian.JIRA>
In-Reply-To: <JIRA.13111087.1508530316000@Atlassian.JIRA>
References: <JIRA.13111087.1508530316000@Atlassian.JIRA> <JIRA.13111087.1508530316495@jira-lw-us.apache.org>
Subject: [jira] [Updated] (KAFKA-6101) Reconnecting to broker does not
 exponentially backoff
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 20 Oct 2017 22:56:07 -0000


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

Ted Yu updated KAFKA-6101:
--------------------------
    Attachment:     (was: 6101.v1.txt)

> 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, 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)