[
https://issues.apache.org/jira/browse/AMBARI-20761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367134#comment-16367134
]
Hudson commented on AMBARI-20761:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8744 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8744/])
AMBARI-20761 Update zookeeper.connect description (Bharat Viswanadham
(aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=f08d487be627f14fce19dc5b726957f49c772a2d])
* (edit)
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/configuration/kafka-broker.xml
> 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
> Fix For: trunk
>
> Attachments: AMBARI-20761.PATCH
>
>
> <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
(v7.6.3#76005)
