[
https://issues.apache.org/jira/browse/KAFKA-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500473#comment-14500473
]
Gwen Shapira commented on KAFKA-2088:
-------------------------------------
I think the main problem here is that someone mistyping the zookeeper chroot
path (or points a consumer at the wrong ZK) looks indistinguishable from
someone starting a consumer before the cluster exists. The first is far more
common though (at least in my experience), so it will be nice to warn the user
that things are not as he expected.
> kafka-console-consumer.sh should not create zookeeper path when no brokers
> found and chroot was set in zookeeper.connect
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-2088
> URL: https://issues.apache.org/jira/browse/KAFKA-2088
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 0.8.2.1
> Reporter: Zhiqiang He
> Assignee: Zhiqiang He
> Priority: Minor
> Attachments: kafka-2088.1.patch
>
>
> 1. set server.properties
> server.properties:
> zookeeper.connect =
> 192.168.0.10:2181,192.168.0.10:2181,192.168.0.10:2181/kafka
> 2 default zookeeepr path:
> [zk: 192.168.0.10:2181(CONNECTED) 10] ls /
> [zookeeper, kafka, storm]
> 3.start console consumer use a not exist topic and zookeeper address without
> chroot.
> [root@stream client_0402]# kafka-console-consumer.sh --zookeeper
> 192.168.0.10:2181 --topic test --from-beginning
> [2015-04-03 18:15:28,599] WARN
> [console-consumer-63060_stream-1428056127990-d35ca648], no brokers found when
> trying to rebalance. (kafka.consumer.ZookeeperConsumerConnector)
> 4.then "/consumer" and "/brokers" path was create in zookeeper.
> [zk: 192.168.0.10:2181(CONNECTED) 2] ls /
> [zookeeper, consumers, kafka, storm, brokers]
> so it is a bug. consumer should not create "/consumer" and "/brokers" path .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
