[
https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895265#comment-15895265
]
ASF GitHub Bot commented on KAFKA-2857:
---------------------------------------
GitHub user vahidhashemian opened a pull request:
https://github.com/apache/kafka/pull/2636
MINOR: Follow up to KAFKA-2857
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vahidhashemian/kafka minor/kafka-2857-followup
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2636.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 #2636
----
----
> ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when
> describing a non-existent group before the offset topic is created
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-2857
> URL: https://issues.apache.org/jira/browse/KAFKA-2857
> Project: Kafka
> Issue Type: Bug
> Components: tools
> Reporter: Ismael Juma
> Assignee: Vahid Hashemian
> Priority: Minor
> Fix For: 0.11.0.0
>
>
> If we describe a non-existing group before the offset topic is created, like
> the following:
> {code}
> bin/kafka-consumer-groups.sh --bootstrap-server localhost:9092 --new-consumer
> --describe --group gggg
> {code}
> We get the following error:
> {code}
> Error while executing consumer group command The group coordinator is not
> available.
> org.apache.kafka.common.errors.GroupCoordinatorNotAvailableException: The
> group coordinator is not available.
> {code}
> The exception is thrown in the `adminClient.describeConsumerGroup` call. We
> can't interpret this exception as meaning that the group doesn't exist
> because it could also be thrown f all replicas for a offset topic partition
> are down (as explained by Jun).
> Jun also suggested that we should distinguish if a coordinator is not
> available from the case where a coordinator doesn't exist.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
