kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Gustafson (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 Tue, 14 Jun 2016 03:10:05 GMT

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

Jason Gustafson commented on KAFKA-2857:
----------------------------------------

[~vahid] That's a good question. Maybe we can get clarification from [~ijuma] or [~junrao],
but the previous sentence in the description suggests maybe the intent is to distinguish the
case of a group not existing? I think it would be fine here to give the user a message which
tells them that the offsets topic is unavailable and points out that it takes a little time
on a new cluster to create it. But if we can't find the coordinator, then there's really no
way to know whether the group "exists" or not.

> 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