kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ishita Mandhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created
Date Thu, 23 Jun 2016 21:00:20 GMT

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

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

So it seems like we need to check if the offsets topic exists or not and we can do this check
right before a call to findCoordinator() is made in the describeGroup function() here - https://github.com/apache/kafka/blob/404b696bea58aca17fbe528aed03cb3c94516c39/core/src/main/scala/kafka/admin/AdminClient.scala#L125.
If the offsets topic doesn’t exist, we can throw an exception and this is the only check
we need to do to resolve the jira based on what I understand. Does this seem like the right
approach to take? 

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

Mime
View raw message