kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jun...@apache.org
Subject [02/17] kafka-site git commit: update 0.9.0 docs
Date Fri, 13 Nov 2015 17:40:24 GMT
http://git-wip-us.apache.org/repos/asf/kafka-site/blob/e047c4b2/090/kafka_config.html
----------------------------------------------------------------------
diff --git a/090/kafka_config.html b/090/kafka_config.html
index 2125b6e..c56b29e 100644
--- a/090/kafka_config.html
+++ b/090/kafka_config.html
@@ -1,268 +1,268 @@
-<table>
+<table class="data-table"><tbody>
 <tr>
 <th>Name</th>
+<th>Description</th>
 <th>Type</th>
 <th>Default</th>
 <th>Valid Values</th>
 <th>Importance</th>
-<th>Description</th>
 </tr>
 <tr>
-<td>zookeeper.connect</td><td>string</td><td></td><td></td><td>high</td><td>Zookeeper host string</td></tr>
+<td>zookeeper.connect</td><td>Zookeeper host string</td><td>string</td><td></td><td></td><td>high</td></tr>
 <tr>
-<td>advertised.host.name</td><td>string</td><td>null</td><td></td><td>high</td><td>Hostname to publish to ZooKeeper for clients to use. In IaaS environments, this may need to be different from the interface to which the broker binds. If this is not set, it will use the value for "host.name" if configured. Otherwise it will use the value returned from java.net.InetAddress.getCanonicalHostName().</td></tr>
+<td>advertised.host.name</td><td>Hostname to publish to ZooKeeper for clients to use. In IaaS environments, this may need to be different from the interface to which the broker binds. If this is not set, it will use the value for "host.name" if configured. Otherwise it will use the value returned from java.net.InetAddress.getCanonicalHostName().</td><td>string</td><td>null</td><td></td><td>high</td></tr>
 <tr>
-<td>advertised.listeners</td><td>string</td><td>null</td><td></td><td>high</td><td>Listeners to publish to ZooKeeper for clients to use, if different than the listeners above. In IaaS environments, this may need to be different from the interface to which the broker binds. If this is not set, the value for "listeners" will be used.</td></tr>
+<td>advertised.listeners</td><td>Listeners to publish to ZooKeeper for clients to use, if different than the listeners above. In IaaS environments, this may need to be different from the interface to which the broker binds. If this is not set, the value for "listeners" will be used.</td><td>string</td><td>null</td><td></td><td>high</td></tr>
 <tr>
-<td>advertised.port</td><td>int</td><td>null</td><td></td><td>high</td><td>The port to publish to ZooKeeper for clients to use. In IaaS environments, this may need to be different from the port to which the broker binds. If this is not set, it will publish the same port that the broker binds to.</td></tr>
+<td>advertised.port</td><td>The port to publish to ZooKeeper for clients to use. In IaaS environments, this may need to be different from the port to which the broker binds. If this is not set, it will publish the same port that the broker binds to.</td><td>int</td><td>null</td><td></td><td>high</td></tr>
 <tr>
-<td>auto.create.topics.enable</td><td>boolean</td><td>true</td><td></td><td>high</td><td>Enable auto creation of topic on the server</td></tr>
+<td>auto.create.topics.enable</td><td>Enable auto creation of topic on the server</td><td>boolean</td><td>true</td><td></td><td>high</td></tr>
 <tr>
-<td>auto.leader.rebalance.enable</td><td>boolean</td><td>true</td><td></td><td>high</td><td>Enables auto leader balancing. A background thread checks and triggers leader balance if required at regular intervals</td></tr>
+<td>auto.leader.rebalance.enable</td><td>Enables auto leader balancing. A background thread checks and triggers leader balance if required at regular intervals</td><td>boolean</td><td>true</td><td></td><td>high</td></tr>
 <tr>
-<td>background.threads</td><td>int</td><td>10</td><td>[1,...]</td><td>high</td><td>The number of threads to use for various background processing tasks</td></tr>
+<td>background.threads</td><td>The number of threads to use for various background processing tasks</td><td>int</td><td>10</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>broker.id</td><td>int</td><td>-1</td><td></td><td>high</td><td>The broker id for this server. To avoid conflicts between zookeeper generated brokerId and user's config.brokerId added MaxReservedBrokerId and zookeeper sequence starts from MaxReservedBrokerId + 1.</td></tr>
+<td>broker.id</td><td>The broker id for this server. To avoid conflicts between zookeeper generated brokerId and user's config.brokerId added MaxReservedBrokerId and zookeeper sequence starts from MaxReservedBrokerId + 1.</td><td>int</td><td>-1</td><td></td><td>high</td></tr>
 <tr>
-<td>compression.type</td><td>string</td><td>producer</td><td></td><td>high</td><td>Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', lz4). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer.</td></tr>
+<td>compression.type</td><td>Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', lz4). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer.</td><td>string</td><td>producer</td><td></td><td>high</td></tr>
 <tr>
-<td>delete.topic.enable</td><td>boolean</td><td>false</td><td></td><td>high</td><td>Enables delete topic. Delete topic through the admin tool will have no effect if this config is turned off</td></tr>
+<td>delete.topic.enable</td><td>Enables delete topic. Delete topic through the admin tool will have no effect if this config is turned off</td><td>boolean</td><td>false</td><td></td><td>high</td></tr>
 <tr>
-<td>host.name</td><td>string</td><td>""</td><td></td><td>high</td><td>hostname of broker. If this is set, it will only bind to this address. If this is not set, it will bind to all interfaces</td></tr>
+<td>host.name</td><td>hostname of broker. If this is set, it will only bind to this address. If this is not set, it will bind to all interfaces</td><td>string</td><td>""</td><td></td><td>high</td></tr>
 <tr>
-<td>leader.imbalance.check.interval.seconds</td><td>long</td><td>300</td><td></td><td>high</td><td>The frequency with which the partition rebalance check is triggered by the controller</td></tr>
+<td>leader.imbalance.check.interval.seconds</td><td>The frequency with which the partition rebalance check is triggered by the controller</td><td>long</td><td>300</td><td></td><td>high</td></tr>
 <tr>
-<td>leader.imbalance.per.broker.percentage</td><td>int</td><td>10</td><td></td><td>high</td><td>The ratio of leader imbalance allowed per broker. The controller would trigger a leader balance if it goes above this value per broker. The value is specified in percentage.</td></tr>
+<td>leader.imbalance.per.broker.percentage</td><td>The ratio of leader imbalance allowed per broker. The controller would trigger a leader balance if it goes above this value per broker. The value is specified in percentage.</td><td>int</td><td>10</td><td></td><td>high</td></tr>
 <tr>
-<td>listeners</td><td>string</td><td>null</td><td></td><td>high</td><td>Listener List - Comma-separated list of URIs we will listen on and their protocols.
+<td>listeners</td><td>Listener List - Comma-separated list of URIs we will listen on and their protocols.
  Specify hostname as 0.0.0.0 to bind to all interfaces.
  Leave hostname empty to bind to default interface.
  Examples of legal listener lists:
  PLAINTEXT://myhost:9092,TRACE://:9091
  PLAINTEXT://0.0.0.0:9092, TRACE://localhost:9093
-</td></tr>
+</td><td>string</td><td>null</td><td></td><td>high</td></tr>
 <tr>
-<td>log.dir</td><td>string</td><td>/tmp/kafka-logs</td><td></td><td>high</td><td>The directory in which the log data is kept (supplemental for log.dirs property)</td></tr>
+<td>log.dir</td><td>The directory in which the log data is kept (supplemental for log.dirs property)</td><td>string</td><td>/tmp/kafka-logs</td><td></td><td>high</td></tr>
 <tr>
-<td>log.dirs</td><td>string</td><td>null</td><td></td><td>high</td><td>The directories in which the log data is kept. If not set, the value in log.dir is used</td></tr>
+<td>log.dirs</td><td>The directories in which the log data is kept. If not set, the value in log.dir is used</td><td>string</td><td>null</td><td></td><td>high</td></tr>
 <tr>
-<td>log.flush.interval.messages</td><td>long</td><td>9223372036854775807</td><td>[1,...]</td><td>high</td><td>The number of messages accumulated on a log partition before messages are flushed to disk </td></tr>
+<td>log.flush.interval.messages</td><td>The number of messages accumulated on a log partition before messages are flushed to disk </td><td>long</td><td>9223372036854775807</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>log.flush.interval.ms</td><td>long</td><td>null</td><td></td><td>high</td><td>The maximum time in ms that a message in any topic is kept in memory before flushed to disk. If not set, the value in log.flush.scheduler.interval.ms is used</td></tr>
+<td>log.flush.interval.ms</td><td>The maximum time in ms that a message in any topic is kept in memory before flushed to disk. If not set, the value in log.flush.scheduler.interval.ms is used</td><td>long</td><td>null</td><td></td><td>high</td></tr>
 <tr>
-<td>log.flush.offset.checkpoint.interval.ms</td><td>int</td><td>60000</td><td>[0,...]</td><td>high</td><td>The frequency with which we update the persistent record of the last flush which acts as the log recovery point</td></tr>
+<td>log.flush.offset.checkpoint.interval.ms</td><td>The frequency with which we update the persistent record of the last flush which acts as the log recovery point</td><td>int</td><td>60000</td><td>[0,...]</td><td>high</td></tr>
 <tr>
-<td>log.flush.scheduler.interval.ms</td><td>long</td><td>9223372036854775807</td><td></td><td>high</td><td>The frequency in ms that the log flusher checks whether any log needs to be flushed to disk</td></tr>
+<td>log.flush.scheduler.interval.ms</td><td>The frequency in ms that the log flusher checks whether any log needs to be flushed to disk</td><td>long</td><td>9223372036854775807</td><td></td><td>high</td></tr>
 <tr>
-<td>log.retention.bytes</td><td>long</td><td>-1</td><td></td><td>high</td><td>The maximum size of the log before deleting it</td></tr>
+<td>log.retention.bytes</td><td>The maximum size of the log before deleting it</td><td>long</td><td>-1</td><td></td><td>high</td></tr>
 <tr>
-<td>log.retention.hours</td><td>int</td><td>168</td><td></td><td>high</td><td>The number of hours to keep a log file before deleting it (in hours), tertiary to log.retention.ms property</td></tr>
+<td>log.retention.hours</td><td>The number of hours to keep a log file before deleting it (in hours), tertiary to log.retention.ms property</td><td>int</td><td>168</td><td></td><td>high</td></tr>
 <tr>
-<td>log.retention.minutes</td><td>int</td><td>null</td><td></td><td>high</td><td>The number of minutes to keep a log file before deleting it (in minutes), secondary to log.retention.ms property. If not set, the value in log.retention.hours is used</td></tr>
+<td>log.retention.minutes</td><td>The number of minutes to keep a log file before deleting it (in minutes), secondary to log.retention.ms property. If not set, the value in log.retention.hours is used</td><td>int</td><td>null</td><td></td><td>high</td></tr>
 <tr>
-<td>log.retention.ms</td><td>long</td><td>null</td><td></td><td>high</td><td>The number of milliseconds to keep a log file before deleting it (in milliseconds), If not set, the value in log.retention.minutes is used</td></tr>
+<td>log.retention.ms</td><td>The number of milliseconds to keep a log file before deleting it (in milliseconds), If not set, the value in log.retention.minutes is used</td><td>long</td><td>null</td><td></td><td>high</td></tr>
 <tr>
-<td>log.roll.hours</td><td>int</td><td>168</td><td>[1,...]</td><td>high</td><td>The maximum time before a new log segment is rolled out (in hours), secondary to log.roll.ms property</td></tr>
+<td>log.roll.hours</td><td>The maximum time before a new log segment is rolled out (in hours), secondary to log.roll.ms property</td><td>int</td><td>168</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>log.roll.jitter.hours</td><td>int</td><td>0</td><td>[0,...]</td><td>high</td><td>The maximum jitter to subtract from logRollTimeMillis (in hours), secondary to log.roll.jitter.ms property</td></tr>
+<td>log.roll.jitter.hours</td><td>The maximum jitter to subtract from logRollTimeMillis (in hours), secondary to log.roll.jitter.ms property</td><td>int</td><td>0</td><td>[0,...]</td><td>high</td></tr>
 <tr>
-<td>log.roll.jitter.ms</td><td>long</td><td>null</td><td></td><td>high</td><td>The maximum jitter to subtract from logRollTimeMillis (in milliseconds). If not set, the value in log.roll.jitter.hours is used</td></tr>
+<td>log.roll.jitter.ms</td><td>The maximum jitter to subtract from logRollTimeMillis (in milliseconds). If not set, the value in log.roll.jitter.hours is used</td><td>long</td><td>null</td><td></td><td>high</td></tr>
 <tr>
-<td>log.roll.ms</td><td>long</td><td>null</td><td></td><td>high</td><td>The maximum time before a new log segment is rolled out (in milliseconds). If not set, the value in log.roll.hours is used</td></tr>
+<td>log.roll.ms</td><td>The maximum time before a new log segment is rolled out (in milliseconds). If not set, the value in log.roll.hours is used</td><td>long</td><td>null</td><td></td><td>high</td></tr>
 <tr>
-<td>log.segment.bytes</td><td>int</td><td>1073741824</td><td>[14,...]</td><td>high</td><td>The maximum size of a single log file</td></tr>
+<td>log.segment.bytes</td><td>The maximum size of a single log file</td><td>int</td><td>1073741824</td><td>[14,...]</td><td>high</td></tr>
 <tr>
-<td>log.segment.delete.delay.ms</td><td>long</td><td>60000</td><td>[0,...]</td><td>high</td><td>The amount of time to wait before deleting a file from the filesystem</td></tr>
+<td>log.segment.delete.delay.ms</td><td>The amount of time to wait before deleting a file from the filesystem</td><td>long</td><td>60000</td><td>[0,...]</td><td>high</td></tr>
 <tr>
-<td>message.max.bytes</td><td>int</td><td>1000012</td><td>[0,...]</td><td>high</td><td>The maximum size of message that the server can receive</td></tr>
+<td>message.max.bytes</td><td>The maximum size of message that the server can receive</td><td>int</td><td>1000012</td><td>[0,...]</td><td>high</td></tr>
 <tr>
-<td>min.insync.replicas</td><td>int</td><td>1</td><td>[1,...]</td><td>high</td><td>define the minimum number of replicas in ISR needed to satisfy a produce request with required.acks=-1 (or all)</td></tr>
+<td>min.insync.replicas</td><td>define the minimum number of replicas in ISR needed to satisfy a produce request with required.acks=-1 (or all)</td><td>int</td><td>1</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>num.io.threads</td><td>int</td><td>8</td><td>[1,...]</td><td>high</td><td>The number of io threads that the server uses for carrying out network requests</td></tr>
+<td>num.io.threads</td><td>The number of io threads that the server uses for carrying out network requests</td><td>int</td><td>8</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>num.network.threads</td><td>int</td><td>3</td><td>[1,...]</td><td>high</td><td>the number of network threads that the server uses for handling network requests</td></tr>
+<td>num.network.threads</td><td>the number of network threads that the server uses for handling network requests</td><td>int</td><td>3</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>num.recovery.threads.per.data.dir</td><td>int</td><td>1</td><td>[1,...]</td><td>high</td><td>The number of threads per data directory to be used for log recovery at startup and flushing at shutdown</td></tr>
+<td>num.recovery.threads.per.data.dir</td><td>The number of threads per data directory to be used for log recovery at startup and flushing at shutdown</td><td>int</td><td>1</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>num.replica.fetchers</td><td>int</td><td>1</td><td></td><td>high</td><td>Number of fetcher threads used to replicate messages from a source broker. Increasing this value can increase the degree of I/O parallelism in the follower broker.</td></tr>
+<td>num.replica.fetchers</td><td>Number of fetcher threads used to replicate messages from a source broker. Increasing this value can increase the degree of I/O parallelism in the follower broker.</td><td>int</td><td>1</td><td></td><td>high</td></tr>
 <tr>
-<td>offset.metadata.max.bytes</td><td>int</td><td>4096</td><td></td><td>high</td><td>The maximum size for a metadata entry associated with an offset commit</td></tr>
+<td>offset.metadata.max.bytes</td><td>The maximum size for a metadata entry associated with an offset commit</td><td>int</td><td>4096</td><td></td><td>high</td></tr>
 <tr>
-<td>offsets.commit.required.acks</td><td>short</td><td>-1</td><td></td><td>high</td><td>The required acks before the commit can be accepted. In general, the default (-1) should not be overridden</td></tr>
+<td>offsets.commit.required.acks</td><td>The required acks before the commit can be accepted. In general, the default (-1) should not be overridden</td><td>short</td><td>-1</td><td></td><td>high</td></tr>
 <tr>
-<td>offsets.commit.timeout.ms</td><td>int</td><td>5000</td><td>[1,...]</td><td>high</td><td>Offset commit will be delayed until all replicas for the offsets topic receive the commit or this timeout is reached. This is similar to the producer request timeout.</td></tr>
+<td>offsets.commit.timeout.ms</td><td>Offset commit will be delayed until all replicas for the offsets topic receive the commit or this timeout is reached. This is similar to the producer request timeout.</td><td>int</td><td>5000</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>offsets.load.buffer.size</td><td>int</td><td>5242880</td><td>[1,...]</td><td>high</td><td>Batch size for reading from the offsets segments when loading offsets into the cache.</td></tr>
+<td>offsets.load.buffer.size</td><td>Batch size for reading from the offsets segments when loading offsets into the cache.</td><td>int</td><td>5242880</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>offsets.retention.check.interval.ms</td><td>long</td><td>600000</td><td>[1,...]</td><td>high</td><td>Frequency at which to check for stale offsets</td></tr>
+<td>offsets.retention.check.interval.ms</td><td>Frequency at which to check for stale offsets</td><td>long</td><td>600000</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>offsets.retention.minutes</td><td>int</td><td>1440</td><td>[1,...]</td><td>high</td><td>Log retention window in minutes for offsets topic</td></tr>
+<td>offsets.retention.minutes</td><td>Log retention window in minutes for offsets topic</td><td>int</td><td>1440</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>offsets.topic.compression.codec</td><td>int</td><td>0</td><td></td><td>high</td><td>Compression codec for the offsets topic - compression may be used to achieve "atomic" commits</td></tr>
+<td>offsets.topic.compression.codec</td><td>Compression codec for the offsets topic - compression may be used to achieve "atomic" commits</td><td>int</td><td>0</td><td></td><td>high</td></tr>
 <tr>
-<td>offsets.topic.num.partitions</td><td>int</td><td>50</td><td>[1,...]</td><td>high</td><td>The number of partitions for the offset commit topic (should not change after deployment)</td></tr>
+<td>offsets.topic.num.partitions</td><td>The number of partitions for the offset commit topic (should not change after deployment)</td><td>int</td><td>50</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>offsets.topic.replication.factor</td><td>short</td><td>3</td><td>[1,...]</td><td>high</td><td>The replication factor for the offsets topic (set higher to ensure availability). To ensure that the effective replication factor of the offsets topic is the configured value, the number of alive brokers has to be at least the replication factor at the time of the first request for the offsets topic. If not, either the offsets topic creation will fail or it will get a replication factor of min(alive brokers, configured replication factor)</td></tr>
+<td>offsets.topic.replication.factor</td><td>The replication factor for the offsets topic (set higher to ensure availability). To ensure that the effective replication factor of the offsets topic is the configured value, the number of alive brokers has to be at least the replication factor at the time of the first request for the offsets topic. If not, either the offsets topic creation will fail or it will get a replication factor of min(alive brokers, configured replication factor)</td><td>short</td><td>3</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>offsets.topic.segment.bytes</td><td>int</td><td>104857600</td><td>[1,...]</td><td>high</td><td>The offsets topic segment bytes should be kept relatively small in order to facilitate faster log compaction and cache loads</td></tr>
+<td>offsets.topic.segment.bytes</td><td>The offsets topic segment bytes should be kept relatively small in order to facilitate faster log compaction and cache loads</td><td>int</td><td>104857600</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>port</td><td>int</td><td>9092</td><td></td><td>high</td><td>the port to listen and accept connections on</td></tr>
+<td>port</td><td>the port to listen and accept connections on</td><td>int</td><td>9092</td><td></td><td>high</td></tr>
 <tr>
-<td>queued.max.requests</td><td>int</td><td>500</td><td>[1,...]</td><td>high</td><td>The number of queued requests allowed before blocking the network threads</td></tr>
+<td>queued.max.requests</td><td>The number of queued requests allowed before blocking the network threads</td><td>int</td><td>500</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>quota.consumer.default</td><td>long</td><td>9223372036854775807</td><td>[1,...]</td><td>high</td><td>Any consumer distinguished by clientId/consumer group will get throttled if it fetches more bytes than this value per-second</td></tr>
+<td>quota.consumer.default</td><td>Any consumer distinguished by clientId/consumer group will get throttled if it fetches more bytes than this value per-second</td><td>long</td><td>9223372036854775807</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>quota.producer.default</td><td>long</td><td>9223372036854775807</td><td>[1,...]</td><td>high</td><td>Any producer distinguished by clientId will get throttled if it produces more bytes than this value per-second</td></tr>
+<td>quota.producer.default</td><td>Any producer distinguished by clientId will get throttled if it produces more bytes than this value per-second</td><td>long</td><td>9223372036854775807</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>replica.fetch.max.bytes</td><td>int</td><td>1048576</td><td></td><td>high</td><td>The number of byes of messages to attempt to fetch</td></tr>
+<td>replica.fetch.max.bytes</td><td>The number of byes of messages to attempt to fetch</td><td>int</td><td>1048576</td><td></td><td>high</td></tr>
 <tr>
-<td>replica.fetch.min.bytes</td><td>int</td><td>1</td><td></td><td>high</td><td>Minimum bytes expected for each fetch response. If not enough bytes, wait up to replicaMaxWaitTimeMs</td></tr>
+<td>replica.fetch.min.bytes</td><td>Minimum bytes expected for each fetch response. If not enough bytes, wait up to replicaMaxWaitTimeMs</td><td>int</td><td>1</td><td></td><td>high</td></tr>
 <tr>
-<td>replica.fetch.wait.max.ms</td><td>int</td><td>500</td><td></td><td>high</td><td>max wait time for each fetcher request issued by follower replicas. This value should always be less than the replica.lag.time.max.ms at all times to prevent frequent shrinking of ISR for low throughput topics</td></tr>
+<td>replica.fetch.wait.max.ms</td><td>max wait time for each fetcher request issued by follower replicas. This value should always be less than the replica.lag.time.max.ms at all times to prevent frequent shrinking of ISR for low throughput topics</td><td>int</td><td>500</td><td></td><td>high</td></tr>
 <tr>
-<td>replica.high.watermark.checkpoint.interval.ms</td><td>long</td><td>5000</td><td></td><td>high</td><td>The frequency with which the high watermark is saved out to disk</td></tr>
+<td>replica.high.watermark.checkpoint.interval.ms</td><td>The frequency with which the high watermark is saved out to disk</td><td>long</td><td>5000</td><td></td><td>high</td></tr>
 <tr>
-<td>replica.lag.time.max.ms</td><td>long</td><td>10000</td><td></td><td>high</td><td>If a follower hasn't sent any fetch requests or hasn't consumed up to the leaders log end offset for at least this time, the leader will remove the follower from isr</td></tr>
+<td>replica.lag.time.max.ms</td><td>If a follower hasn't sent any fetch requests or hasn't consumed up to the leaders log end offset for at least this time, the leader will remove the follower from isr</td><td>long</td><td>10000</td><td></td><td>high</td></tr>
 <tr>
-<td>replica.socket.receive.buffer.bytes</td><td>int</td><td>65536</td><td></td><td>high</td><td>The socket receive buffer for network requests</td></tr>
+<td>replica.socket.receive.buffer.bytes</td><td>The socket receive buffer for network requests</td><td>int</td><td>65536</td><td></td><td>high</td></tr>
 <tr>
-<td>replica.socket.timeout.ms</td><td>int</td><td>30000</td><td></td><td>high</td><td>The socket timeout for network requests. Its value should be at least replica.fetch.wait.max.ms</td></tr>
+<td>replica.socket.timeout.ms</td><td>The socket timeout for network requests. Its value should be at least replica.fetch.wait.max.ms</td><td>int</td><td>30000</td><td></td><td>high</td></tr>
 <tr>
-<td>request.timeout.ms</td><td>int</td><td>30000</td><td></td><td>high</td><td>The configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted.</td></tr>
+<td>request.timeout.ms</td><td>The configuration controls the maximum amount of time the client will wait for the response of a request. If the response is not received before the timeout elapses the client will resend the request if necessary or fail the request if retries are exhausted.</td><td>int</td><td>30000</td><td></td><td>high</td></tr>
 <tr>
-<td>socket.receive.buffer.bytes</td><td>int</td><td>102400</td><td></td><td>high</td><td>The SO_RCVBUF buffer of the socket sever sockets</td></tr>
+<td>socket.receive.buffer.bytes</td><td>The SO_RCVBUF buffer of the socket sever sockets</td><td>int</td><td>102400</td><td></td><td>high</td></tr>
 <tr>
-<td>socket.request.max.bytes</td><td>int</td><td>104857600</td><td>[1,...]</td><td>high</td><td>The maximum number of bytes in a socket request</td></tr>
+<td>socket.request.max.bytes</td><td>The maximum number of bytes in a socket request</td><td>int</td><td>104857600</td><td>[1,...]</td><td>high</td></tr>
 <tr>
-<td>socket.send.buffer.bytes</td><td>int</td><td>102400</td><td></td><td>high</td><td>The SO_SNDBUF buffer of the socket sever sockets</td></tr>
+<td>socket.send.buffer.bytes</td><td>The SO_SNDBUF buffer of the socket sever sockets</td><td>int</td><td>102400</td><td></td><td>high</td></tr>
 <tr>
-<td>unclean.leader.election.enable</td><td>boolean</td><td>true</td><td></td><td>high</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>
+<td>unclean.leader.election.enable</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><td>boolean</td><td>true</td><td></td><td>high</td></tr>
 <tr>
-<td>zookeeper.connection.timeout.ms</td><td>int</td><td>null</td><td></td><td>high</td><td>The max time that the client waits to establish a connection to zookeeper. If not set, the value in zookeeper.session.timeout.ms is used</td></tr>
+<td>zookeeper.connection.timeout.ms</td><td>The max time that the client waits to establish a connection to zookeeper. If not set, the value in zookeeper.session.timeout.ms is used</td><td>int</td><td>null</td><td></td><td>high</td></tr>
 <tr>
-<td>zookeeper.session.timeout.ms</td><td>int</td><td>6000</td><td></td><td>high</td><td>Zookeeper session timeout</td></tr>
+<td>zookeeper.session.timeout.ms</td><td>Zookeeper session timeout</td><td>int</td><td>6000</td><td></td><td>high</td></tr>
 <tr>
-<td>zookeeper.set.acl</td><td>boolean</td><td>false</td><td></td><td>high</td><td>Set client to use secure ACLs</td></tr>
+<td>zookeeper.set.acl</td><td>Set client to use secure ACLs</td><td>boolean</td><td>false</td><td></td><td>high</td></tr>
 <tr>
-<td>connections.max.idle.ms</td><td>long</td><td>600000</td><td></td><td>medium</td><td>Idle connections timeout: the server socket processor threads close the connections that idle more than this</td></tr>
+<td>connections.max.idle.ms</td><td>Idle connections timeout: the server socket processor threads close the connections that idle more than this</td><td>long</td><td>600000</td><td></td><td>medium</td></tr>
 <tr>
-<td>controlled.shutdown.enable</td><td>boolean</td><td>true</td><td></td><td>medium</td><td>Enable controlled shutdown of the server</td></tr>
+<td>controlled.shutdown.enable</td><td>Enable controlled shutdown of the server</td><td>boolean</td><td>true</td><td></td><td>medium</td></tr>
 <tr>
-<td>controlled.shutdown.max.retries</td><td>int</td><td>3</td><td></td><td>medium</td><td>Controlled shutdown can fail for multiple reasons. This determines the number of retries when such failure happens</td></tr>
+<td>controlled.shutdown.max.retries</td><td>Controlled shutdown can fail for multiple reasons. This determines the number of retries when such failure happens</td><td>int</td><td>3</td><td></td><td>medium</td></tr>
 <tr>
-<td>controlled.shutdown.retry.backoff.ms</td><td>long</td><td>5000</td><td></td><td>medium</td><td>Before each retry, the system needs time to recover from the state that caused the previous failure (Controller fail over, replica lag etc). This config determines the amount of time to wait before retrying.</td></tr>
+<td>controlled.shutdown.retry.backoff.ms</td><td>Before each retry, the system needs time to recover from the state that caused the previous failure (Controller fail over, replica lag etc). This config determines the amount of time to wait before retrying.</td><td>long</td><td>5000</td><td></td><td>medium</td></tr>
 <tr>
-<td>controller.socket.timeout.ms</td><td>int</td><td>30000</td><td></td><td>medium</td><td>The socket timeout for controller-to-broker channels</td></tr>
+<td>controller.socket.timeout.ms</td><td>The socket timeout for controller-to-broker channels</td><td>int</td><td>30000</td><td></td><td>medium</td></tr>
 <tr>
-<td>default.replication.factor</td><td>int</td><td>1</td><td></td><td>medium</td><td>default replication factors for automatically created topics</td></tr>
+<td>default.replication.factor</td><td>default replication factors for automatically created topics</td><td>int</td><td>1</td><td></td><td>medium</td></tr>
 <tr>
-<td>fetch.purgatory.purge.interval.requests</td><td>int</td><td>1000</td><td></td><td>medium</td><td>The purge interval (in number of requests) of the fetch request purgatory</td></tr>
+<td>fetch.purgatory.purge.interval.requests</td><td>The purge interval (in number of requests) of the fetch request purgatory</td><td>int</td><td>1000</td><td></td><td>medium</td></tr>
 <tr>
-<td>group.max.session.timeout.ms</td><td>int</td><td>30000</td><td></td><td>medium</td><td>The maximum allowed session timeout for registered consumers</td></tr>
+<td>group.max.session.timeout.ms</td><td>The maximum allowed session timeout for registered consumers</td><td>int</td><td>30000</td><td></td><td>medium</td></tr>
 <tr>
-<td>group.min.session.timeout.ms</td><td>int</td><td>6000</td><td></td><td>medium</td><td>The minimum allowed session timeout for registered consumers</td></tr>
+<td>group.min.session.timeout.ms</td><td>The minimum allowed session timeout for registered consumers</td><td>int</td><td>6000</td><td></td><td>medium</td></tr>
 <tr>
-<td>inter.broker.protocol.version</td><td>string</td><td>0.9.0.X</td><td></td><td>medium</td><td>Specify which version of the inter-broker protocol will be used.
+<td>inter.broker.protocol.version</td><td>Specify which version of the inter-broker protocol will be used.
  This is typically bumped after all brokers were upgraded to a new version.
- Example of some valid values are: 0.8.0, 0.8.1, 0.8.1.1, 0.8.2, 0.8.2.0, 0.8.2.1, 0.9.0.0, 0.9.0.1 Check ApiVersion for the full list.</td></tr>
+ Example of some valid values are: 0.8.0, 0.8.1, 0.8.1.1, 0.8.2, 0.8.2.0, 0.8.2.1, 0.9.0.0, 0.9.0.1 Check ApiVersion for the full list.</td><td>string</td><td>0.9.0.X</td><td></td><td>medium</td></tr>
 <tr>
-<td>log.cleaner.backoff.ms</td><td>long</td><td>15000</td><td>[0,...]</td><td>medium</td><td>The amount of time to sleep when there are no logs to clean</td></tr>
+<td>log.cleaner.backoff.ms</td><td>The amount of time to sleep when there are no logs to clean</td><td>long</td><td>15000</td><td>[0,...]</td><td>medium</td></tr>
 <tr>
-<td>log.cleaner.dedupe.buffer.size</td><td>long</td><td>524288000</td><td></td><td>medium</td><td>The total memory used for log deduplication across all cleaner threads</td></tr>
+<td>log.cleaner.dedupe.buffer.size</td><td>The total memory used for log deduplication across all cleaner threads</td><td>long</td><td>524288000</td><td></td><td>medium</td></tr>
 <tr>
-<td>log.cleaner.delete.retention.ms</td><td>long</td><td>86400000</td><td></td><td>medium</td><td>How long are delete records retained?</td></tr>
+<td>log.cleaner.delete.retention.ms</td><td>How long are delete records retained?</td><td>long</td><td>86400000</td><td></td><td>medium</td></tr>
 <tr>
-<td>log.cleaner.enable</td><td>boolean</td><td>false</td><td></td><td>medium</td><td>Should we enable log cleaning?</td></tr>
+<td>log.cleaner.enable</td><td>Should we enable log cleaning?</td><td>boolean</td><td>false</td><td></td><td>medium</td></tr>
 <tr>
-<td>log.cleaner.io.buffer.load.factor</td><td>double</td><td>0.9</td><td></td><td>medium</td><td>Log cleaner dedupe buffer load factor. The percentage full the dedupe buffer can become. A higher value will allow more log to be cleaned at once but will lead to more hash collisions</td></tr>
+<td>log.cleaner.io.buffer.load.factor</td><td>Log cleaner dedupe buffer load factor. The percentage full the dedupe buffer can become. A higher value will allow more log to be cleaned at once but will lead to more hash collisions</td><td>double</td><td>0.9</td><td></td><td>medium</td></tr>
 <tr>
-<td>log.cleaner.io.buffer.size</td><td>int</td><td>524288</td><td>[0,...]</td><td>medium</td><td>The total memory used for log cleaner I/O buffers across all cleaner threads</td></tr>
+<td>log.cleaner.io.buffer.size</td><td>The total memory used for log cleaner I/O buffers across all cleaner threads</td><td>int</td><td>524288</td><td>[0,...]</td><td>medium</td></tr>
 <tr>
-<td>log.cleaner.io.max.bytes.per.second</td><td>double</td><td>1.7976931348623157E308</td><td></td><td>medium</td><td>The log cleaner will be throttled so that the sum of its read and write i/o will be less than this value on average</td></tr>
+<td>log.cleaner.io.max.bytes.per.second</td><td>The log cleaner will be throttled so that the sum of its read and write i/o will be less than this value on average</td><td>double</td><td>1.7976931348623157E308</td><td></td><td>medium</td></tr>
 <tr>
-<td>log.cleaner.min.cleanable.ratio</td><td>double</td><td>0.5</td><td></td><td>medium</td><td>The minimum ratio of dirty log to total log for a log to eligible for cleaning</td></tr>
+<td>log.cleaner.min.cleanable.ratio</td><td>The minimum ratio of dirty log to total log for a log to eligible for cleaning</td><td>double</td><td>0.5</td><td></td><td>medium</td></tr>
 <tr>
-<td>log.cleaner.threads</td><td>int</td><td>1</td><td>[0,...]</td><td>medium</td><td>The number of background threads to use for log cleaning</td></tr>
+<td>log.cleaner.threads</td><td>The number of background threads to use for log cleaning</td><td>int</td><td>1</td><td>[0,...]</td><td>medium</td></tr>
 <tr>
-<td>log.cleanup.policy</td><td>string</td><td>delete</td><td>[compact, delete]</td><td>medium</td><td>The default cleanup policy for segments beyond the retention window, must be either "delete" or "compact"</td></tr>
+<td>log.cleanup.policy</td><td>The default cleanup policy for segments beyond the retention window, must be either "delete" or "compact"</td><td>string</td><td>delete</td><td>[compact, delete]</td><td>medium</td></tr>
 <tr>
-<td>log.index.interval.bytes</td><td>int</td><td>4096</td><td>[0,...]</td><td>medium</td><td>The interval with which we add an entry to the offset index</td></tr>
+<td>log.index.interval.bytes</td><td>The interval with which we add an entry to the offset index</td><td>int</td><td>4096</td><td>[0,...]</td><td>medium</td></tr>
 <tr>
-<td>log.index.size.max.bytes</td><td>int</td><td>10485760</td><td>[4,...]</td><td>medium</td><td>The maximum size in bytes of the offset index</td></tr>
+<td>log.index.size.max.bytes</td><td>The maximum size in bytes of the offset index</td><td>int</td><td>10485760</td><td>[4,...]</td><td>medium</td></tr>
 <tr>
-<td>log.preallocate</td><td>boolean</td><td>false</td><td></td><td>medium</td><td>Should pre allocate file when create new segment? If you are using Kafka on Windows, you probably need to set it to true.</td></tr>
+<td>log.preallocate</td><td>Should pre allocate file when create new segment? If you are using Kafka on Windows, you probably need to set it to true.</td><td>boolean</td><td>false</td><td></td><td>medium</td></tr>
 <tr>
-<td>log.retention.check.interval.ms</td><td>long</td><td>300000</td><td>[1,...]</td><td>medium</td><td>The frequency in milliseconds that the log cleaner checks whether any log is eligible for deletion</td></tr>
+<td>log.retention.check.interval.ms</td><td>The frequency in milliseconds that the log cleaner checks whether any log is eligible for deletion</td><td>long</td><td>300000</td><td>[1,...]</td><td>medium</td></tr>
 <tr>
-<td>max.connections.per.ip</td><td>int</td><td>2147483647</td><td>[1,...]</td><td>medium</td><td>The maximum number of connections we allow from each ip address</td></tr>
+<td>max.connections.per.ip</td><td>The maximum number of connections we allow from each ip address</td><td>int</td><td>2147483647</td><td>[1,...]</td><td>medium</td></tr>
 <tr>
-<td>max.connections.per.ip.overrides</td><td>string</td><td>""</td><td></td><td>medium</td><td>Per-ip or hostname overrides to the default maximum number of connections</td></tr>
+<td>max.connections.per.ip.overrides</td><td>Per-ip or hostname overrides to the default maximum number of connections</td><td>string</td><td>""</td><td></td><td>medium</td></tr>
 <tr>
-<td>num.partitions</td><td>int</td><td>1</td><td>[1,...]</td><td>medium</td><td>The default number of log partitions per topic</td></tr>
+<td>num.partitions</td><td>The default number of log partitions per topic</td><td>int</td><td>1</td><td>[1,...]</td><td>medium</td></tr>
 <tr>
-<td>principal.builder.class</td><td>class</td><td>class org.apache.kafka.common.security.auth.DefaultPrincipalBuilder</td><td></td><td>medium</td><td>principal builder to generate a java Principal. This config is optional for client.</td></tr>
+<td>principal.builder.class</td><td>principal builder to generate a java Principal. This config is optional for client.</td><td>class</td><td>class org.apache.kafka.common.security.auth.DefaultPrincipalBuilder</td><td></td><td>medium</td></tr>
 <tr>
-<td>producer.purgatory.purge.interval.requests</td><td>int</td><td>1000</td><td></td><td>medium</td><td>The purge interval (in number of requests) of the producer request purgatory</td></tr>
+<td>producer.purgatory.purge.interval.requests</td><td>The purge interval (in number of requests) of the producer request purgatory</td><td>int</td><td>1000</td><td></td><td>medium</td></tr>
 <tr>
-<td>replica.fetch.backoff.ms</td><td>int</td><td>1000</td><td>[0,...]</td><td>medium</td><td>The amount of time to sleep when fetch partition error occurs.</td></tr>
+<td>replica.fetch.backoff.ms</td><td>The amount of time to sleep when fetch partition error occurs.</td><td>int</td><td>1000</td><td>[0,...]</td><td>medium</td></tr>
 <tr>
-<td>reserved.broker.max.id</td><td>int</td><td>1000</td><td>[0,...]</td><td>medium</td><td>reserved.broker.max.id</td></tr>
+<td>reserved.broker.max.id</td><td>reserved.broker.max.id</td><td>int</td><td>1000</td><td>[0,...]</td><td>medium</td></tr>
 <tr>
-<td>sasl.kerberos.kinit.cmd</td><td>string</td><td>/usr/bin/kinit</td><td></td><td>medium</td><td>Kerberos kinit command path. Default is /usr/bin/kinit</td></tr>
+<td>sasl.kerberos.kinit.cmd</td><td>Kerberos kinit command path. Default is /usr/bin/kinit</td><td>string</td><td>/usr/bin/kinit</td><td></td><td>medium</td></tr>
 <tr>
-<td>sasl.kerberos.min.time.before.relogin</td><td>long</td><td>60000</td><td></td><td>medium</td><td>Login thread sleep time between refresh attempts.</td></tr>
+<td>sasl.kerberos.min.time.before.relogin</td><td>Login thread sleep time between refresh attempts.</td><td>long</td><td>60000</td><td></td><td>medium</td></tr>
 <tr>
-<td>sasl.kerberos.principal.to.local.rules</td><td>list</td><td>[DEFAULT]</td><td></td><td>medium</td><td>A list of rules for mapping from principal names to short names (typically operating system usernames). The rules are evaluated in order and the first rule that matches a principal name is used to map it to a short name. Any later rules in the list are ignored. By default, principal names of the form <username>/<hostname>@<REALM> are mapped to <username>.</td></tr>
+<td>sasl.kerberos.principal.to.local.rules</td><td>A list of rules for mapping from principal names to short names (typically operating system usernames). The rules are evaluated in order and the first rule that matches a principal name is used to map it to a short name. Any later rules in the list are ignored. By default, principal names of the form <username>/<hostname>@<REALM> are mapped to <username>.</td><td>list</td><td>[DEFAULT]</td><td></td><td>medium</td></tr>
 <tr>
-<td>sasl.kerberos.service.name</td><td>string</td><td>null</td><td></td><td>medium</td><td>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</td></tr>
+<td>sasl.kerberos.service.name</td><td>The Kerberos principal name that Kafka runs as. This can be defined either in Kafka's JAAS config or in Kafka's config.</td><td>string</td><td>null</td><td></td><td>medium</td></tr>
 <tr>
-<td>sasl.kerberos.ticket.renew.jitter</td><td>double</td><td>0.05</td><td></td><td>medium</td><td>Percentage of random jitter added to the renewal time.</td></tr>
+<td>sasl.kerberos.ticket.renew.jitter</td><td>Percentage of random jitter added to the renewal time.</td><td>double</td><td>0.05</td><td></td><td>medium</td></tr>
 <tr>
-<td>sasl.kerberos.ticket.renew.window.factor</td><td>double</td><td>0.8</td><td></td><td>medium</td><td>Login thread will sleep until the specified window factor of time from last refresh to ticket's expiry has been reached, at which time it will try to renew the ticket.</td></tr>
+<td>sasl.kerberos.ticket.renew.window.factor</td><td>Login thread will sleep until the specified window factor of time from last refresh to ticket's expiry has been reached, at which time it will try to renew the ticket.</td><td>double</td><td>0.8</td><td></td><td>medium</td></tr>
 <tr>
-<td>security.inter.broker.protocol</td><td>string</td><td>PLAINTEXT</td><td></td><td>medium</td><td>Security protocol used to communicate between brokers. Defaults to plain text.</td></tr>
+<td>security.inter.broker.protocol</td><td>Security protocol used to communicate between brokers. Defaults to plain text.</td><td>string</td><td>PLAINTEXT</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.cipher.suites</td><td>list</td><td>null</td><td></td><td>medium</td><td>A list of cipher suites. This is a named combination of authentication, encryption, MAC and key exchange algorithm used to negotiate the security settings for a network connection using TLS or SSL network protocol.By default all the available cipher suites are supported.</td></tr>
+<td>ssl.cipher.suites</td><td>A list of cipher suites. This is a named combination of authentication, encryption, MAC and key exchange algorithm used to negotiate the security settings for a network connection using TLS or SSL network protocol.By default all the available cipher suites are supported.</td><td>list</td><td>null</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.client.auth</td><td>string</td><td>none</td><td>[required, requested, none]</td><td>medium</td><td>Configures kafka broker to request client authentication. The following settings are common:  <ul> <li><code>ssl.want.client.auth=required</code> If set to required client authentication is required. <li><code>ssl.client.auth=requested</code> This means client authentication is optional. unlike requested , if this option is set client can choose not to provide authentication information about itself <li><code>ssl.client.auth=none</code> This means client authentication is not needed.</td></tr>
+<td>ssl.client.auth</td><td>Configures kafka broker to request client authentication. The following settings are common:  <ul> <li><code>ssl.want.client.auth=required</code> If set to required client authentication is required. <li><code>ssl.client.auth=requested</code> This means client authentication is optional. unlike requested , if this option is set client can choose not to provide authentication information about itself <li><code>ssl.client.auth=none</code> This means client authentication is not needed.</td><td>string</td><td>none</td><td>[required, requested, none]</td><td>medium</td></tr>
 <tr>
-<td>ssl.enabled.protocols</td><td>list</td><td>[TLSv1.2, TLSv1.1, TLSv1]</td><td></td><td>medium</td><td>The list of protocols enabled for SSL connections. TLSv1.2, TLSv1.1 and TLSv1 are enabled by default.</td></tr>
+<td>ssl.enabled.protocols</td><td>The list of protocols enabled for SSL connections. TLSv1.2, TLSv1.1 and TLSv1 are enabled by default.</td><td>list</td><td>[TLSv1.2, TLSv1.1, TLSv1]</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.key.password</td><td>string</td><td>null</td><td></td><td>medium</td><td>The password of the private key in the key store file. This is optional for client.</td></tr>
+<td>ssl.key.password</td><td>The password of the private key in the key store file. This is optional for client.</td><td>password</td><td>null</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.keymanager.algorithm</td><td>string</td><td>SunX509</td><td></td><td>medium</td><td>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</td></tr>
+<td>ssl.keymanager.algorithm</td><td>The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.</td><td>string</td><td>SunX509</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.keystore.location</td><td>string</td><td>null</td><td></td><td>medium</td><td>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</td></tr>
+<td>ssl.keystore.location</td><td>The location of the key store file. This is optional for client and can be used for two-way authentication for client.</td><td>string</td><td>null</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.keystore.password</td><td>string</td><td>null</td><td></td><td>medium</td><td>The store password for the key store file.This is optional for client and only needed if ssl.keystore.location is configured. </td></tr>
+<td>ssl.keystore.password</td><td>The store password for the key store file.This is optional for client and only needed if ssl.keystore.location is configured. </td><td>password</td><td>null</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.keystore.type</td><td>string</td><td>JKS</td><td></td><td>medium</td><td>The file format of the key store file. This is optional for client. Default value is JKS</td></tr>
+<td>ssl.keystore.type</td><td>The file format of the key store file. This is optional for client. Default value is JKS</td><td>string</td><td>JKS</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.protocol</td><td>string</td><td>TLS</td><td></td><td>medium</td><td>The SSL protocol used to generate the SSLContext. Default setting is TLS, which is fine for most cases. Allowed values in recent JVMs are TLS, TLSv1.1 and TLSv1.2. SSL, SSLv2 and SSLv3 may be supported in older JVMs, but their usage is discouraged due to known security vulnerabilities.</td></tr>
+<td>ssl.protocol</td><td>The SSL protocol used to generate the SSLContext. Default setting is TLS, which is fine for most cases. Allowed values in recent JVMs are TLS, TLSv1.1 and TLSv1.2. SSL, SSLv2 and SSLv3 may be supported in older JVMs, but their usage is discouraged due to known security vulnerabilities.</td><td>string</td><td>TLS</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.provider</td><td>string</td><td>null</td><td></td><td>medium</td><td>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</td></tr>
+<td>ssl.provider</td><td>The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.</td><td>string</td><td>null</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.trustmanager.algorithm</td><td>string</td><td>PKIX</td><td></td><td>medium</td><td>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</td></tr>
+<td>ssl.trustmanager.algorithm</td><td>The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.</td><td>string</td><td>PKIX</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.truststore.location</td><td>string</td><td>null</td><td></td><td>medium</td><td>The location of the trust store file. </td></tr>
+<td>ssl.truststore.location</td><td>The location of the trust store file. </td><td>string</td><td>null</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.truststore.password</td><td>string</td><td>null</td><td></td><td>medium</td><td>The password for the trust store file. </td></tr>
+<td>ssl.truststore.password</td><td>The password for the trust store file. </td><td>password</td><td>null</td><td></td><td>medium</td></tr>
 <tr>
-<td>ssl.truststore.type</td><td>string</td><td>JKS</td><td></td><td>medium</td><td>The file format of the trust store file. Default value is JKS.</td></tr>
+<td>ssl.truststore.type</td><td>The file format of the trust store file. Default value is JKS.</td><td>string</td><td>JKS</td><td></td><td>medium</td></tr>
 <tr>
-<td>authorizer.class.name</td><td>string</td><td>""</td><td></td><td>low</td><td>The authorizer class that should be used for authorization</td></tr>
+<td>authorizer.class.name</td><td>The authorizer class that should be used for authorization</td><td>string</td><td>""</td><td></td><td>low</td></tr>
 <tr>
-<td>metric.reporters</td><td>list</td><td>[]</td><td></td><td>low</td><td>A list of classes to use as metrics reporters. Implementing the <code>MetricReporter</code> interface allows plugging in classes that will be notified of new metric creation. The JmxReporter is always included to register JMX statistics.</td></tr>
+<td>metric.reporters</td><td>A list of classes to use as metrics reporters. Implementing the <code>MetricReporter</code> interface allows plugging in classes that will be notified of new metric creation. The JmxReporter is always included to register JMX statistics.</td><td>list</td><td>[]</td><td></td><td>low</td></tr>
 <tr>
-<td>metrics.num.samples</td><td>int</td><td>2</td><td>[1,...]</td><td>low</td><td>The number of samples maintained to compute metrics.</td></tr>
+<td>metrics.num.samples</td><td>The number of samples maintained to compute metrics.</td><td>int</td><td>2</td><td>[1,...]</td><td>low</td></tr>
 <tr>
-<td>metrics.sample.window.ms</td><td>long</td><td>30000</td><td>[1,...]</td><td>low</td><td>The number of samples maintained to compute metrics.</td></tr>
+<td>metrics.sample.window.ms</td><td>The number of samples maintained to compute metrics.</td><td>long</td><td>30000</td><td>[1,...]</td><td>low</td></tr>
 <tr>
-<td>quota.window.num</td><td>int</td><td>11</td><td>[1,...]</td><td>low</td><td>The number of samples to retain in memory</td></tr>
+<td>quota.window.num</td><td>The number of samples to retain in memory</td><td>int</td><td>11</td><td>[1,...]</td><td>low</td></tr>
 <tr>
-<td>quota.window.size.seconds</td><td>int</td><td>1</td><td>[1,...]</td><td>low</td><td>The time span of each sample</td></tr>
+<td>quota.window.size.seconds</td><td>The time span of each sample</td><td>int</td><td>1</td><td>[1,...]</td><td>low</td></tr>
 <tr>
-<td>ssl.endpoint.identification.algorithm</td><td>string</td><td>null</td><td></td><td>low</td><td>The endpoint identification algorithm to validate server hostname using server certificate. </td></tr>
+<td>ssl.endpoint.identification.algorithm</td><td>The endpoint identification algorithm to validate server hostname using server certificate. </td><td>string</td><td>null</td><td></td><td>low</td></tr>
 <tr>
-<td>zookeeper.sync.time.ms</td><td>int</td><td>2000</td><td></td><td>low</td><td>How far a ZK follower can be behind a ZK leader</td></tr>
-</table>
+<td>zookeeper.sync.time.ms</td><td>How far a ZK follower can be behind a ZK leader</td><td>int</td><td>2000</td><td></td><td>low</td></tr>
+</tbody></table>

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/e047c4b2/090/ops.html
----------------------------------------------------------------------
diff --git a/090/ops.html b/090/ops.html
index 93640b0..af1c15c 100644
--- a/090/ops.html
+++ b/090/ops.html
@@ -135,7 +135,7 @@ Adding servers to a Kafka cluster is easy, just assign them a unique broker id a
 <p>
 The process of migrating data is manually initiated but fully automated. Under the covers what happens is that Kafka will add the new server as a follower of the partition it is migrating and allow it to fully replicate the existing data in that partition. When the new server has fully replicated the contents of this partition and joined the in-sync replica one of the existing replicas will delete their partition's data.
 <p>
-The partition reassignment tool can be used to move partitions across brokers. An ideal partition distribution would ensure even data load and partition sizes across all brokers. In 0.8.1, the partition reassignment tool does not have the capability to automatically study the data distribution in a Kafka cluster and move partitions around to attain an even load distribution. As such, the admin has to figure out which topics or partitions should be moved around. 
+The partition reassignment tool can be used to move partitions across brokers. An ideal partition distribution would ensure even data load and partition sizes across all brokers.
 <p>
 The partition reassignment tool can run in 3 mutually exclusive modes -
 <ul>
@@ -257,7 +257,7 @@ Reassignment of partition [foo2,1] completed successfully
 </pre>
 
 <h4><a id="basic_ops_decommissioning_brokers">Decommissioning brokers</a></h4>
-The partition reassignment tool does not have the ability to automatically generate a reassignment plan for decommissioning brokers yet. As such, the admin has to come up with a reassignment plan to move the replica for all partitions hosted on the broker to be decommissioned, to the rest of the brokers. This can be relatively tedious as the reassignment needs to ensure that all the replicas are not moved from the decommissioned broker to only one other broker. To make this process effortless, we plan to add tooling support for decommissioning brokers in 0.8.2.
+The partition reassignment tool does not have the ability to automatically generate a reassignment plan for decommissioning brokers yet. As such, the admin has to come up with a reassignment plan to move the replica for all partitions hosted on the broker to be decommissioned, to the rest of the brokers. This can be relatively tedious as the reassignment needs to ensure that all the replicas are not moved from the decommissioned broker to only one other broker. To make this process effortless, we plan to add tooling support for decommissioning brokers in the future.
 
 <h4><a id="basic_ops_increase_replication_factor">Increasing replication factor</a></h4>
 Increasing the replication factor of an existing partition is easy. Just specify the extra replicas in the custom reassignment json file and use it with the --execute option to increase the replication factor of the specified partitions. 
@@ -427,7 +427,7 @@ Two configurations that may be important:
 </ul>
 
 <h4><a id="diskandfs">Disks and Filesystem</a></h4>
-We recommend using multiple drives to get good throughput and not sharing the same drives used for Kafka data with application logs or other OS filesystem activity to ensure good latency. As of 0.8 you can either RAID these drives together into a single volume or format and mount each drive as its own directory. Since Kafka has replication the redundancy provided by RAID can also be provided at the application level. This choice has several tradeoffs.
+We recommend using multiple drives to get good throughput and not sharing the same drives used for Kafka data with application logs or other OS filesystem activity to ensure good latency. You can either RAID these drives together into a single volume or format and mount each drive as its own directory. Since Kafka has replication the redundancy provided by RAID can also be provided at the application level. This choice has several tradeoffs.
 <p>
 If you configure multiple data directories partitions will be assigned round-robin to data directories. Each partition will be entirely in one of the data directories. If data is not well balanced among partitions this can lead to load imbalance between disks.
 <p>


Mime
View raw message