[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

["Ishita Mandhan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325152#comment-15325152 ] 

Ishita Mandhan commented on KAFKA-2857:
---------------------------------------

Working on this with [~vahid] and we aren't sure about what the part about all replicas for a offset topic partition being down means. If all __consumer_offsets partitions are down, wouldn't all the brokers be down as well (meaning that all brokers keep the same copy of __consumer_offsets)?

> 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
>            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)