[
https://issues.apache.org/jira/browse/KAFKA-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470168#comment-15470168
]
ASF GitHub Bot commented on KAFKA-4139:
---------------------------------------
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/1831
KAFKA-4139: Reset findCoordinatorFuture when brokers are unavailable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajinisivaram/kafka KAFKA-4139
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1831.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 #1831
----
commit 1f02ef1159f9876f48e075723ce17c738715e827
Author: Rajini Sivaram <rajinisiva...@googlemail.com>
Date: 2016-09-07T09:26:39Z
KAFKA-4139: Reset findCoordinatorFuture when brokers are unavailable
----
> Kafka consumer stuck in ensureCoordinatorReady after broker failure
> -------------------------------------------------------------------
>
> Key: KAFKA-4139
> URL: https://issues.apache.org/jira/browse/KAFKA-4139
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 0.10.0.1
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
>
> In one of our tests with a single broker, consumer is stuck waiting to find
> coordinator after the broker is restarted. {{findCoordinatorFuture}} is never
> reset if {{sendGroupCoordinatorRequest()}} returns
> {{RequestFuture.noBrokersAvailable()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
