You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Bharat Viswanadham (JIRA)" <ji...@apache.org> on 2017/04/13 19:34:41 UTC
[jira] [Updated] (AMBARI-20761) Update propery description for
zookeeper.connect in Kafka Config
[ https://issues.apache.org/jira/browse/AMBARI-20761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharat Viswanadham updated AMBARI-20761:
----------------------------------------
Assignee: Bharat Viswanadham
Status: Patch Available (was: Open)
> Update propery description for zookeeper.connect in Kafka Config
> ----------------------------------------------------------------
>
> Key: AMBARI-20761
> URL: https://issues.apache.org/jira/browse/AMBARI-20761
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Minor
>
> <property>
> <name>zookeeper.connect</name>
> <value>localhost:2181</value>
> <description>
> Zookeeper also allows you to add a "chroot" path which will make all kafka data for this cluster appear under a particular path.
> This is a way to setup multiple Kafka clusters or other applications on the same zookeeper cluster. To do this give a connection
> string in the form hostname1:port1,hostname2:port2,hostname3:port3/chroot/path which would put all this cluster's data under the
> path /chroot/path. Note that you must create this path yourself prior to starting the broker and consumers must use the
> same connection string.
> </description>
> In the description it is said to create path before starting broker and consumer. Actually this is taken care in Kafka. So need to cleanup this.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)