[
https://issues.apache.org/jira/browse/KAFKA-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030503#comment-16030503
]
ASF GitHub Bot commented on KAFKA-5293:
---------------------------------------
GitHub user cmccabe opened a pull request:
https://github.com/apache/kafka/pull/3174
KAFKA-5293. Do not apply exponential backoff if users have overridden…
… reconnect.backoff.ms
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cmccabe/kafka KAFKA-5293
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3174.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 #3174
----
commit 41b1839be4f87516bf771ccd0802c068f8da067c
Author: Colin P. Mccabe <cmcc...@confluent.io>
Date: 2017-05-31T02:15:14Z
KAFKA-5293. Do not apply exponential backoff if users have overridden
reconnect.backoff.ms
----
> Do not apply exponential backoff if users have overridden reconnect.backoff.ms
> ------------------------------------------------------------------------------
>
> Key: KAFKA-5293
> URL: https://issues.apache.org/jira/browse/KAFKA-5293
> Project: Kafka
> Issue Type: Bug
> Reporter: Ismael Juma
> Assignee: Colin P. McCabe
> Priority: Critical
> Fix For: 0.11.0.0
>
>
> The PR for KAFKA-3878 implemented KIP-144 with one exception: it
> automatically enables exponential backoff for the producer and consumer even
> if reconnect.backoff.ms is set by users. The KIP stated that this would not
> be the case.
> As part of this JIRA, we should also add a few unit tests for connectionDelay
> and perhaps consider enabling exponential backoff for Connect and Streams as
> well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
