[ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347193#comment-15347193 ]
Jason Gustafson commented on KAFKA-2857: ---------------------------------------- [~imandhan] I think maybe it can be even simpler. If the error code returned from the GroupCoordinator request is COORDINATOR_NOT_AVAILABLE, then we can print a message as suggested above. So maybe we just need to change {{findCoordinator}} to return an Option instead of throwing? > 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: Ishita Mandhan > 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)