You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/06/01 20:29:04 UTC
[jira] [Updated] (KAFKA-5293) Do not apply exponential backoff if
users have overridden reconnect.backoff.ms
[ https://issues.apache.org/jira/browse/KAFKA-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismael Juma updated KAFKA-5293:
-------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 3174
[https://github.com/apache/kafka/pull/3174]
> 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)