I went ahead and tried this locally and the new topic metadata request does
appear to be the problem. Unfortunately, the tools are bound by the same
compatibility model as the clients, which means there is no guarantee that
they work with older versions. As a workaround, I guess you can use the
consumer-groups.sh script from 0.9 until all the brokers have been upgraded.

-Jason

On Tue, May 24, 2016 at 6:31 PM, tao xiao <xiaotao...@gmail.com> wrote:

> I am pretty sure consumer-group.sh uses tools-log4j.properties
>
> On Tue, 24 May 2016 at 17:59 allen chan <allen.michael.c...@gmail.com>
> wrote:
>
> > Maybe i am doing this wrong
> >
> > [ac...@ekk001.scl ~]$ cat
> > /opt/kafka/kafka_2.11-0.10.0.0/config/log4j.properties
> > ..
> > log4j.rootLogger=DEBUG, kafkaAppender
> > ..
> >
> >
> > See no extra logs when running the consumer-group.sh tool.
> >
> >
> >
> > On Tue, May 24, 2016 at 5:46 PM, Jason Gustafson <ja...@confluent.io>
> > wrote:
> >
> > > Hey Allen,
> > >
> > > Can you turn on DEBUG logging and see if there's another exception?
> First
> > > thought that occurs to me is that it might be the topic metadata
> request
> > > which is actually failing. There was a version bump in 0.10 which would
> > not
> > > be supported by the 0.9 brokers.
> > >
> > > Thanks,
> > > Jason
> > >
> > > On Tue, May 24, 2016 at 5:21 PM, allen chan <
> > allen.michael.c...@gmail.com>
> > > wrote:
> > >
> > > > I upgraded one of my brokers to 0.10.0. I followed the upgrade guide
> > and
> > > > added these to my server.properties:
> > > >
> > > > inter.broker.protocol.version=0.9.0.1
> > > > log.message.format.version=0.9.0.1
> > > >
> > > >
> > > >
> > > > When checking the lag i get this error.
> > > > [ac...@ekk001.scl ~]$  sudo
> > > > /opt/kafka/kafka_2.11-0.10.0.0/bin/kafka-consumer-groups.sh
> > > > --bootstrap-server=ekk001.scl:9092,ekk002.scl:9092 --new-consumer
> > > > --describe --group fdm_indexers
> > > > Error while executing consumer group command Request
> GROUP_COORDINATOR
> > > > failed on brokers List(ekk001.scl:9092 (id: -1 rack: null),
> > > ekk002.scl:9092
> > > > (id: -2 rack: null))
> > > > java.lang.RuntimeException: Request GROUP_COORDINATOR failed on
> brokers
> > > > List(ekk001.scl:9092 (id: -1 rack: null), ekk002.scl:9092 (id: -2
> rack:
> > > > null))
> > > > at kafka.admin.AdminClient.sendAnyNode(AdminClient.scala:67)
> > > > at kafka.admin.AdminClient.findCoordinator(AdminClient.scala:72)
> > > > at kafka.admin.AdminClient.describeGroup(AdminClient.scala:125)
> > > > at
> kafka.admin.AdminClient.describeConsumerGroup(AdminClient.scala:147)
> > > > at
> > > >
> > > >
> > >
> >
> kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService.describeGroup(ConsumerGroupCommand.scala:315)
> > > > at
> > > >
> > > >
> > >
> >
> kafka.admin.ConsumerGroupCommand$ConsumerGroupService$class.describe(ConsumerGroupCommand.scala:86)
> > > > at
> > > >
> > > >
> > >
> >
> kafka.admin.ConsumerGroupCommand$KafkaConsumerGroupService.describe(ConsumerGroupCommand.scala:303)
> > > > at
> > kafka.admin.ConsumerGroupCommand$.main(ConsumerGroupCommand.scala:65)
> > > > at kafka.admin.ConsumerGroupCommand.main(ConsumerGroupCommand.scala)
> > > >
> > > >
> > > > I happen to still have the 0.9.0.1 bits on disk so i ran that
> > > > kafka-consumer-group.sh and that works just fine.
> > > > [ac...@ekk001.scl ~]$  sudo
> > > > /opt/kafka/kafka_2.11-0.9.0.1/bin/kafka-consumer-groups.sh
> > > > --bootstrap-server=ekk001.scl:9092,ekk002.scl:9092 --new-consumer
> > > > --describe --group fdm_indexers
> > > > GROUP, TOPIC, PARTITION, CURRENT OFFSET, LOG END OFFSET, LAG, OWNER
> > > > fdm_indexers, freedom_logs, 1, 1778672075, 1778672075, 0,
> > > > lsi016.scl_/10.x.92.156
> > > > fdm_indexers, freedom_logs, 5, 433366037, 433366037, 0,
> > > > lsi099.scl_/10.x.92.160
> > > > fdm_indexers, freedom_logs, 3, 1778672009, 1778672009, 0,
> > > > lsi018.scl_/10.x.92.158
> > > > fdm_indexers, freedom_logs, 2, 1778672066, 1778672066, 0,
> > > > lsi017.scl_/10.x.92.157
> > > > fdm_indexers, freedom_logs, 0, 1778672030, 1778672030, 0,
> > > > lsi015.scl_/10.x.92.155
> > > > fdm_indexers, freedom_logs, 4, 499098735, 499098735, 0,
> > > > lsi019.scl_/10.x.92.159
> > > >
> > > > I browsed through the release notes and couldn't isolate anything
> that
> > > > would be related.
> > > >
> > > > Any one have idea why this is happening?
> > > > --
> > > > Allen Michael Chan
> > > >
> > >
> >
> >
> >
> > --
> > Allen Michael Chan
> >
>

Reply via email to