kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jun...@apache.org
Subject svn commit: r1653637 - /kafka/site/082/configuration.html
Date Wed, 21 Jan 2015 19:52:16 GMT
Author: junrao
Date: Wed Jan 21 19:52:15 2015
New Revision: 1653637

URL: http://svn.apache.org/r1653637
Log:
add missing config values for 0.8.2

Modified:
    kafka/site/082/configuration.html

Modified: kafka/site/082/configuration.html
URL: http://svn.apache.org/viewvc/kafka/site/082/configuration.html?rev=1653637&r1=1653636&r2=1653637&view=diff
==============================================================================
--- kafka/site/082/configuration.html (original)
+++ kafka/site/082/configuration.html Wed Jan 21 19:52:15 2015
@@ -217,6 +217,11 @@ ZooKeeper also allows you to add a "chro
       <td>The frequency with which we checkpoint the last flush point for logs for
recovery. You should not need to change this.</td>
     </tr>
     <tr>
+      <td>log.segment.delete.delay.ms</td>
+      <td>60000</td>
+      <td>the amount of time to wait before deleting a file from the filesystem.</td>
+    </tr>
+    <tr>
       <td>auto.create.topics.enable</td>
       <td>true</td>
       <td>Enable auto creation of topic on the server.  If this is set to true then
attempts to produce data or fetch metadata for a non-existent topic will automatically create
it with the default replication factor and number of partitions.</td>
@@ -545,6 +550,11 @@ The essential consumer configurations ar
       <td nowrap>1024 * 1024</td>
       <td>The number of byes of messages to attempt to fetch for each topic-partition
in each fetch request. These bytes will be read into memory for each partition, so this helps
control the memory used by the consumer. The fetch request size must be at least as large
as the maximum message size the server allows or else it is possible for the producer to send
messages larger than the consumer can fetch.</td>
     </tr>
+     <tr>
+      <td>num.consumer.fetchers</td>
+      <td colspan="1">1</td>
+      <td>The number fetcher threads used to fetch data.</td>
+    </tr>
     <tr>
       <td>auto.commit.enable</td>
       <td colspan="1">true</td>
@@ -597,6 +607,16 @@ The essential consumer configurations ar
       <td colspan="1">-1</td>
       <td>Throw a timeout exception to the consumer if no message is available for
consumption after the specified interval</td>
     </tr>
+     <tr>
+      <td>exclude.internal.topics</td>
+      <td colspan="1">true</td>
+      <td>Whether messages from internal topics (such as offsets) should be exposed
to the consumer.</td>
+    </tr>
+     <tr>
+      <td>partition.assignment.strategy</td>
+      <td colspan="1">range</td>
+      <td>Select a strategy for assigning partitions to consumer streams. Possible
values: range, roundrobin.</td>
+    </tr>
     <tr>
       <td>client.id</td>
       <td colspan="1">group id value</td>



Mime
View raw message