You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2016/05/04 23:59:12 UTC

[jira] [Created] (KAFKA-3659) Consumer handle coordinator connection blackout period

Jason Gustafson created KAFKA-3659:
--------------------------------------

             Summary: Consumer handle coordinator connection blackout period
                 Key: KAFKA-3659
                 URL: https://issues.apache.org/jira/browse/KAFKA-3659
             Project: Kafka
          Issue Type: Bug
          Components: consumer
    Affects Versions: 0.9.0.1, 0.9.0.0
            Reporter: Jason Gustafson
            Assignee: Jason Gustafson


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)