[jira] [Resolved] (KAFKA-3659) Consumer does not handle coordinator connection blackout period gracefully

["Ewen Cheslack-Postava (JIRA)" <ji...@apache.org>]

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

Ewen Cheslack-Postava resolved KAFKA-3659.
------------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.0.0
                   0.10.1.0

Issue resolved by pull request 1322
[https://github.com/apache/kafka/pull/1322]

> Consumer does not handle coordinator connection blackout period gracefully
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-3659
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3659
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>    Affects Versions: 0.9.0.0, 0.9.0.1
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>             Fix For: 0.10.1.0, 0.10.0.0
>
>
> Currently when the connection to the coordinator is closed, the consumer will immediately try to rediscover the coordinator and reconnect to it. This is fine as it is, but the NetworkClient enforces a blackout period before it will allow the reconnect to be attempted. This causes the following cycle which continues in a fairly tight loop until the blackout period has completed:
> 1. Notice connection failure (i.e. DISCONNECTED state in ConnectionStates)
> 2. Send GroupCoordinator request to rediscover coordinator.
> 3. Attempt to connect to coordinator.
> 4. Go back to 1.
> To fix this, we should avoid rediscovery while the connection is blacked out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)