You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ishita Mandhan (JIRA)" <ji...@apache.org> on 2017/01/27 22:49:24 UTC
[jira] [Assigned] (KAFKA-2857) ConsumerGroupCommand throws
GroupCoordinatorNotAvailableException when describing a non-existent group
before the offset topic is created
[ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ishita Mandhan reassigned KAFKA-2857:
-------------------------------------
Assignee: Vahid Hashemian (was: Ishita Mandhan)
> 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
>
> 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.4#6332)