You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Samuel Zhou (JIRA)" <ji...@apache.org> on 2015/10/05 20:57:29 UTC

[jira] [Issue Comment Deleted] (KAFKA-2452) enable new consumer in mirror maker

     [ https://issues.apache.org/jira/browse/KAFKA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Samuel Zhou updated KAFKA-2452:
-------------------------------
    Comment: was deleted

(was: Looks like it can't find zookeeper path for the topic in the consumer group(zk1, zk2 and zk3 are zookeeper hosts):

bin/kafka-consumer-offset-checker.sh --topic ssl.test1 --group sslMirrorMaker --zookeeper zk1:2181,zk2:2181,zk3:2181/kafka_ssl

[2015-10-05 13:41:43,162] WARN WARNING: ConsumerOffsetChecker is deprecated and will be dropped in releases following 0.9.0. Use ConsumerGroupCommand instead. (kafka.tools.ConsumerOffsetChecker$)
Exiting due to: org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /consumers/sslMirrorMaker/offsets/ssl.test1/6.

There are 2 issues here:

I use the chroot syntax to specify the zookeeper root path but ConsumerOffsetChecker still checked the consumer group from root(/) not the root path I specified(/kafka_ssl). 

When I use the "sslMirrorMaker" as the consumer group for MirrorMaker, there is no folder named sslMirrorMaker created in zookeeper path /consumers nor /kafka_ssl/consumers since I use bootstrap servers instead of zookeeper.connect in consumer.properties.)

> enable new consumer in mirror maker
> -----------------------------------
>
>                 Key: KAFKA-2452
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2452
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: core
>    Affects Versions: 0.9.0.0
>            Reporter: Jun Rao
>            Assignee: Jiangjie Qin
>            Priority: Blocker
>             Fix For: 0.9.0.0
>
>
> We need to an an option to enable the new consumer in mirror maker.



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