[
https://issues.apache.org/jira/browse/KAFKA-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977348#comment-14977348
]
ASF GitHub Bot commented on KAFKA-2677:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/349
> Coordinator disconnects not propagated to new consumer
> ------------------------------------------------------
>
> Key: KAFKA-2677
> URL: https://issues.apache.org/jira/browse/KAFKA-2677
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Fix For: 0.9.0.0
>
>
> Currently, disconnects by the coordinator are not always seen by the
> consumer. This can result in a long delay after the old coordinator has
> shutdown or failed before the consumer knows that it needs to find the new
> coordinator. The NetworkClient makes socket disconnects available to users in
> two ways:
> 1. through a flag in the ClientResponse object for requests pending when the
> disconnect occurred, and
> 2. through the connectionFailed() method.
> The first method clearly cannot be depended on since it only helps when a
> request is pending, which is relatively rare for the connection with the
> coordinator. Instead, we can probably use the second method with a little
> rework of ConsumerNetworkClient to check for failed connections immediately
> after returning from poll().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
