You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by ju...@apache.org on 2014/10/27 21:53:02 UTC
svn commit: r1634682 - in /kafka/site/082: configuration.html ops.html
Author: junrao
Date: Mon Oct 27 20:53:01 2014
New Revision: 1634682
URL: http://svn.apache.org/r1634682
Log:
update the config and jmx doc for 082
Modified:
kafka/site/082/configuration.html
kafka/site/082/ops.html
Modified: kafka/site/082/configuration.html
URL: http://svn.apache.org/viewvc/kafka/site/082/configuration.html?rev=1634682&r1=1634681&r2=1634682&view=diff
==============================================================================
--- kafka/site/082/configuration.html (original)
+++ kafka/site/082/configuration.html Mon Oct 27 20:53:01 2014
@@ -112,8 +112,8 @@ ZooKeeper also allows you to add a "chro
<td>The log for a topic partition is stored as a directory of segment files. This setting controls the size to which a segment file will grow before a new segment is rolled over in the log. This setting can be overridden on a per-topic basis (see <a href="#topic-config">the per-topic configuration section</a>).</td>
</tr>
<tr>
- <td>log.roll.hours</td>
- <td>24 * 7</td>
+ <td>log.roll.{ms,hours}</td>
+ <td>24 * 7 hours</td>
<td>This setting will force Kafka to roll a new log segment even if the log.segment.bytes size has not been reached. This setting can be overridden on a per-topic basis (see <a href="#topic-config">the per-topic configuration section</a>).</td>
</tr>
<tr>
@@ -122,7 +122,7 @@ ZooKeeper also allows you to add a "chro
<td>This can take either the value <i>delete</i> or <i>compact</i>. If <i>delete</i> is set, log segments will be deleted when they reach the size or time limits set. If <i>compact</i> is set <a href="#compaction">log compaction</a> will be used to clean out obsolete records. This setting can be overridden on a per-topic basis (see <a href="#topic-config">the per-topic configuration section</a>).</td>
</tr>
<tr>
- <td>log.retention.{minutes,hours}</td>
+ <td>log.retention.{ms,minutes,hours}</td>
<td>7 days</td>
<td>The amount of time to keep a log segment before it is deleted, i.e. the default data retention window for all topics. Note that if both log.retention.minutes and log.retention.bytes are both set we delete a segment when either limit is exceeded. This setting can be overridden on a per-topic basis (see <a href="#topic-config">the per-topic configuration section</a>).</td>
</tr>
@@ -310,7 +310,7 @@ ZooKeeper also allows you to add a "chro
</tr>
<tr>
<td>controlled.shutdown.enable</td>
- <td>false</td>
+ <td>true</td>
<td>Enable controlled shutdown of the broker. If enabled, the broker will move all leaders on it to some other brokers before shutting itself down. This reduces the unavailability window during shutdown.</td>
</tr>
<tr>
@@ -325,7 +325,7 @@ ZooKeeper also allows you to add a "chro
</tr>
<tr>
<td>auto.leader.rebalance.enable</td>
- <td>false</td>
+ <td>true</td>
<td>If this is enabled the controller will automatically try to balance leadership for partitions among the brokers by periodically returning leadership to the "preferred" replica for each partition if it is available.</td>
</tr>
<tr>
@@ -344,6 +344,41 @@ ZooKeeper also allows you to add a "chro
<td>1024</td>
<td>The maximum amount of metadata to allow clients to save with their offsets.</td>
</tr>
+ <tr>
+ <td>max.connections.per.ip</td>
+ <td>Int.MaxValue</td>
+ <td>The maximum number of connections that a broker allows from each ip address.</td>
+ </tr>
+ <tr>
+ <td>max.connections.per.ip.overrides</td>
+ <td></td>
+ <td>Per-ip or hostname overrides to the default maximum number of connections.</td>
+ </tr>
+ <tr>
+ <td>connections.max.idle.ms</td>
+ <td>600000</td>
+ <td>Idle connections timeout: the server socket processor threads close the connections that idle more than this.</td>
+ </tr>
+ <tr>
+ <td>log.roll.jitter.{ms,hours}</td>
+ <td>600000</td>
+ <td>The maximum jitter to subtract from logRollTimeMillis.</td>
+ </tr>
+ <tr>
+ <td>num.recovery.threads.per.data.dir</td>
+ <td>600000</td>
+ <td>The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.</td>
+ </tr>
+ <tr>
+ <td>unclean.leader.election.enable</td>
+ <td>true</td>
+ <td>Indicates whether to enable replicas not in the ISR set to be elected as leader as a last resort, even though doing so may result in data loss.</td>
+ </tr>
+ <tr>
+ <td>delete.topic.enable</td>
+ <td>false</td>
+ <td>Enable delete topic.</td>
+ </tr>
</tbody></table>
<p>More details about broker configuration can be found in the scala class <code>kafka.server.KafkaConfig</code>.</p>
@@ -448,6 +483,12 @@ The following are the topic-level config
<td>log.roll.hours</td>
<td>This configuration controls the period of time after which Kafka will force the log to roll even if the segment file isn't full to ensure that retention can delete or compact old data.</td>
</tr>
+ <tr>
+ <td>segment.jitter.ms</td>
+ <td>0</td>
+ <td>log.roll.jitter.{ms,hours}</td>
+ <td>The maximum jitter to subtract from logRollTimeMillis.</td>
+ </tr>
</table>
<h3><a id="consumerconfigs">3.2 Consumer Configs</a></h3>
Modified: kafka/site/082/ops.html
URL: http://svn.apache.org/viewvc/kafka/site/082/ops.html?rev=1634682&r1=1634681&r2=1634682&view=diff
==============================================================================
--- kafka/site/082/ops.html (original)
+++ kafka/site/082/ops.html Mon Oct 27 20:53:01 2014
@@ -574,6 +574,16 @@ We pay particular we do graphing and ale
<td>"kafka.consumer":name="([-.\w]+)-MaxLag",type="ConsumerFetcherManager"</td>
<td></td>
</tr>
+ <tr>
+ <td>The average fraction of time the network processors are idle</td>
+ <td>"kafka.network":type="SocketServer",name="NetworkProcessorAvgIdlePercent"</td>
+ <td>between 0 and 1, ideally > 0.3</td>
+ </tr>
+ <tr>
+ <td>The average fraction of time the request handler threads are idle</td>
+ <td>"kafka.server":type="KafkaRequestHandlerPool",name="RequestHandlerAvgIdlePercent"</td>
+ <td>between 0 and 1, ideally > 0.3</td>
+ </tr>
</tbody></table>
We recommend monitor GC time and other stats and various server stats such as CPU utilization, I/O service time, etc.