[
https://issues.apache.org/jira/browse/KAFKA-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426344#comment-16426344
]
James Cheng commented on KAFKA-6746:
------------------------------------
The zookeeper.connect config value actually lets you specify a chroot path, but
it appears that the documentation doesn't actually say that. At least, not in
the right place.
Here is something from the old consumer section:
[http://kafka.apache.org/documentation/#oldconsumerconfigs]
{noformat}
The server may also have a ZooKeeper chroot path as part of its ZooKeeper
connection string which puts its data under some path in the global ZooKeeper
namespace. If so the consumer should use the same chroot path in its connection
string. For example to give a chroot path of /chroot/path you would give the
connection string as
hostname1:port1,hostname2:port2,hostname3:port3/chroot/path.
{noformat}
Can you test if that works? And if so, would you be willing to open a pull
request to improve the documentation about this?
> Allow ZK Znode configurable for Kafka broker
> ---------------------------------------------
>
> Key: KAFKA-6746
> URL: https://issues.apache.org/jira/browse/KAFKA-6746
> Project: Kafka
> Issue Type: Improvement
> Reporter: Biju Nair
> Priority: Major
>
> By allowing users to specify the {{Znode}} to be used along with the {{ZK
> Quorum}}, users will be able to reuse a {{ZK}} cluster for many {{Kafka}}
> clusters. This will help in reducing the {{ZK}} cluster footprint especially
> in non production environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
