kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From guozh...@apache.org
Subject svn commit: r1693351 - in /kafka/site: 082/configuration.html 083/configuration.html
Date Wed, 29 Jul 2015 21:44:55 GMT
Author: guozhang
Date: Wed Jul 29 21:44:55 2015
New Revision: 1693351

URL: http://svn.apache.org/r1693351
Log:
KAFKA-2357: Update zookeeper.connect description; patched by David Jacot, reviewed by Guozhang
Wang

Modified:
    kafka/site/082/configuration.html
    kafka/site/083/configuration.html

Modified: kafka/site/082/configuration.html
URL: http://svn.apache.org/viewvc/kafka/site/082/configuration.html?rev=1693351&r1=1693350&r2=1693351&view=diff
==============================================================================
--- kafka/site/082/configuration.html (original)
+++ kafka/site/082/configuration.html Wed Jul 29 21:44:55 2015
@@ -38,7 +38,7 @@ Topic-level configurations and defaults
       <td>null</td>
       <td>Specifies the ZooKeeper connection string in the form <code>hostname:port</code>,
where hostname and port are the host and port for a node in your ZooKeeper cluster. To allow
connecting through other ZooKeeper nodes when that host is down you can also specify multiple
hosts in the form <code>hostname1:port1,hostname2:port2,hostname3:port3</code>.
     <p>
-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 <code>hostname1:port1,hostname2:port2,hostname3:port3/chroot/path</code>
which would put all this cluster's data under the path <code>/chroot/path</code>.
Note that you must create this path yourself prior to starting the broker and consumers must
use the same connection string.</td>
+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 <code>hostname1:port1,hostname2:port2,hostname3:port3/chroot/path</code>
which would put all this cluster's data under the path <code>/chroot/path</code>.
Note that consumers must use the same connection string.</td>
     </tr>
     <tr>
       <td>message.max.bytes</td>

Modified: kafka/site/083/configuration.html
URL: http://svn.apache.org/viewvc/kafka/site/083/configuration.html?rev=1693351&r1=1693350&r2=1693351&view=diff
==============================================================================
--- kafka/site/083/configuration.html (original)
+++ kafka/site/083/configuration.html Wed Jul 29 21:44:55 2015
@@ -38,7 +38,7 @@ Topic-level configurations and defaults
       <td>null</td>
       <td>Specifies the ZooKeeper connection string in the form <code>hostname:port</code>,
where hostname and port are the host and port for a node in your ZooKeeper cluster. To allow
connecting through other ZooKeeper nodes when that host is down you can also specify multiple
hosts in the form <code>hostname1:port1,hostname2:port2,hostname3:port3</code>.
     <p>
-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 <code>hostname1:port1,hostname2:port2,hostname3:port3/chroot/path</code>
which would put all this cluster's data under the path <code>/chroot/path</code>.
Note that you must create this path yourself prior to starting the broker and consumers must
use the same connection string.</td>
+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 <code>hostname1:port1,hostname2:port2,hostname3:port3/chroot/path</code>
which would put all this cluster's data under the path <code>/chroot/path</code>.
Note that consumers must use the same connection string.</td>
     </tr>
     <tr>
       <td>message.max.bytes</td>



Mime
View raw message