Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Fri, 2 Dec 2016 09:41:58 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12914176.1447867021000.421817.1480671718742@Atlassian.JIRA>
In-Reply-To: <JIRA.12914176.1447867021000@Atlassian.JIRA>
References: <JIRA.12914176.1447867021000@Atlassian.JIRA> <JIRA.12914176.1447867021371@arcas>
Subject: [jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws
 GroupCoordinatorNotAvailableException when describing a non-existent group
 before the offset topic is created
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 02 Dec 2016 09:42:00 -0000


    [ https://issues.apache.org/jira/browse/KAFKA-2857?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1571=
4623#comment-15714623 ]=20

ASF GitHub Bot commented on KAFKA-2857:
---------------------------------------

GitHub user imandhan opened a pull request:

    https://github.com/apache/kafka/pull/2203

    KAFKA-2857 ConsumerGroupCommand throws GroupCoordinatorNotAvailableEx=
=E2=80=A6

    =E2=80=A6ception when describing a non-existent group before the offset=
 topic is created #1548=20

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/imandhan/kafka KAFKA-2857-2

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/2203.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2203
   =20
----
commit ea3a0609388d19caf2de6587a5efdbcb851a3224
Author: Ishita Mandhan <imandha@us.ibm.com>
Date:   2016-12-02T09:45:57Z

    KAFKA-2857 ConsumerGroupCommand throws GroupCoordinatorNotAvailableExce=
ption when describing a non-existent group before the offset topic is creat=
ed #1548

----


> ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when de=
scribing 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, l=
ike the following:
> {code}
> bin/kafka-consumer-groups.sh --bootstrap-server localhost:9092 --new-cons=
umer --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 b=
ecause 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 ava=
ilable from the case where a coordinator doesn't exist.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)