[
https://issues.apache.org/jira/browse/KAFKA-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418299#comment-15418299
]
ASF GitHub Bot commented on KAFKA-4034:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/1720
KAFKA-4034: Avoid unnecessary consumer coordinator lookup
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-4034
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1720.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 #1720
----
commit 393e9e56f25bed2cfb3396cce5a10df5b55c3fd4
Author: Jason Gustafson <ja...@confluent.io>
Date: 2016-08-12T03:16:30Z
KAFKA-4034: Avoid unnecessary consumer coordinator lookup
----
> Consumer need not lookup coordinator when using manual assignment
> -----------------------------------------------------------------
>
> Key: KAFKA-4034
> URL: https://issues.apache.org/jira/browse/KAFKA-4034
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 0.9.0.0, 0.9.0.1, 0.10.0.0, 0.10.0.1
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
>
> Currently, we lookup the coordinator even if the user is using manual
> assignment and not storing offsets in Kafka. This seems unnecessary and can
> lead to surprising group authorization failures if the user does not have
> Describe access to the group. We should be able to change the code to only
> lookup the coordinator when we know we are going to use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
