kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Manikumar <manikumar.re...@gmail.com>
Subject Re: kafka-consumers-group.sh version 2.0.0 does not recognize --zookeeper option
Date Thu, 04 Oct 2018 16:44:03 GMT
Deprecated scala consumers/producers are removed from 2.0 release. Old
consumer related options are removed from /kafka-consumer-groups.sh tool.
http://kafka.apache.org/documentation/#upgrade_200_notable

We missed updating some of the docs. Will be fixed in next release docs.

On Thu, Oct 4, 2018 at 10:01 PM Spadoni Marco <Marco.Spadoni@italiaonline.it>
wrote:

> Hi all,
> I installed kafka_2.11-2.0.0 tarball on a CentOS server :
> [kafka@oxelkk-bo-1:~] $ uname -a
> Linux oxelkk-bo-1 3.10.0-862.11.6.el7.x86_64 #1 SMP Tue Aug 14 21:49:04
> UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> [kafka@oxelkk-bo-1:~] $
>
> equipped with this JVM:
> [kafka@oxelkk-bo-1:~] $ java -version
> java version "1.8.0_77"
> Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)
> [kafka@oxelkk-bo-1:~] $
>
> I have a strange behavior of the utility bin/kafka-consumer-groups.sh when
> it is called with --zookeeper option, like:
>
> [kafka@oxelkk-bo-1:~] $
> /store1/elk/run/kafka_2.11-2.0.0/bin/kafka-consumer-groups.sh --zookeeper
> oxelkk-bo-1.iol.local:2181 --list
> Exception in thread "main" joptsimple.UnrecognizedOptionException:
> zookeeper is not a recognized option
>         at
> joptsimple.OptionException.unrecognizedOption(OptionException.java:108)
>         at
> joptsimple.OptionParser.handleLongOptionToken(OptionParser.java:510)
>         at
> joptsimple.OptionParserState$2.handleArgument(OptionParserState.java:56)
>         at joptsimple.OptionParser.parse(OptionParser.java:396)
>         at
> kafka.admin.ConsumerGroupCommand$ConsumerGroupCommandOptions.<init>(ConsumerGroupCommand.scala:725)
>         at
> kafka.admin.ConsumerGroupCommand$.main(ConsumerGroupCommand.scala:42)
>         at
> kafka.admin.ConsumerGroupCommand.main(ConsumerGroupCommand.scala)
> [kafka@oxelkk-bo-1:~] $
>
> Whilst if I use (just for a test) the same utility coming with
> kafka_2.11-0.11.0.0, I have the expected response (the groups are related
> to two Druid Tranquility tasks):
>
> [kafka@oxelkk-bo-1:~] $
> /store1/elk/run/kafka_2.11-0.11.0.0/bin/kafka-consumer-groups.sh
> --zookeeper oxelkk-bo-1.iol.local:2181 --list
> Note: This will only show information about consumers that use ZooKeeper
> (not those using the Java consumer API).
>
> tranquility-kafka-proxy
> tranquility-kafka-ssoeven
> [kafka@oxelkk-bo-1:~] $
>
> I noticed that the documentation for Kafka 2.0.0 at:
> https://kafka.apache.org/documentation/#basic_ops_consumer_lag states:
>
> This tool also works with ZooKeeper-based consumers:
> bin/kafka-consumer-groups.sh --zookeeper localhost:2181 --describe --group
> my-group
>
> Do you have any hint on this behavior?
> Thank you very much,
>
> Marco Spadoni
> Italiaonline S.p.A.
>
>
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify
> postmaster@italiaonline.it .
> www.italiaonline.it
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message