Kafka uses key-value pairs in the <ahref="http://en.wikipedia.org/wiki/.properties">property file format</a> for configuration. These values can be supplied either from a file or programmatically.
Configurations pertinent to topics have both a server default as well an optional per-topic override. If no per-topic configuration is given the server default is used. The override can be set at topic creation time by giving one or more <code>--config</code> options. This example creates a topic named <i>my-topic</i> with a custom max message size and flush rate:
The following are the topic-level configurations. The server's default configuration for this property is given under the Server Default Property heading. A given server default config value only applies to a topic if it does not have an explicit topic config override.
For those interested in the legacy Scala producer configs, information can be found <ahref="http://kafka.apache.org/082/documentation.html#producerconfigs">
The essential old consumer configurations are the following:
<ul>
<li><code>group.id</code>
<li><code>zookeeper.connect</code>
</ul>
<tableclass="data-table">
<tbody><tr>
<th>Property</th>
<th>Default</th>
<th>Description</th>
</tr>
<tr>
<td>group.id</td>
<tdcolspan="1"></td>
<td>A string that uniquely identifies the group of consumer processes to which this consumer belongs. By setting the same group id multiple processes indicate that they are all part of the same consumer group.</td>
</tr>
<tr>
<td>zookeeper.connect</td>
<tdcolspan="1"></td>
<td>Specifies the ZooKeeper connection string in the form <code>hostname:port</code> where host and port are the host and port of a ZooKeeper server. To allow connecting through other ZooKeeper nodes when that ZooKeeper machine is down you can also specify multiple hosts in the form <code>hostname1:port1,hostname2:port2,hostname3:port3</code>.
<p>
The server may also have a ZooKeeper chroot path as part of its ZooKeeper connection string which puts its data under some path in the global ZooKeeper namespace. If so the consumer should use the same chroot path in its connection string. For example to give a chroot path of <code>/chroot/path</code> you would give the connection string as <code>hostname1:port1,hostname2:port2,hostname3:port3/chroot/path</code>.</td>
<td>The socket timeout for network requests. The actual timeout set will be max.fetch.wait + socket.timeout.ms.</td>
</tr>
<tr>
<td>socket.receive.buffer.bytes</td>
<tdcolspan="1">64 * 1024</td>
<td>The socket receive buffer for network requests</td>
</tr>
<tr>
<td>fetch.message.max.bytes</td>
<tdnowrap>1024 * 1024</td>
<td>The number of bytes 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>
<tdcolspan="1">1</td>
<td>The number fetcher threads used to fetch data.</td>
</tr>
<tr>
<td>auto.commit.enable</td>
<tdcolspan="1">true</td>
<td>If true, periodically commit to ZooKeeper the offset of messages already fetched by the consumer. This committed offset will be used when the process fails as the position from which the new consumer will begin.</td>
</tr>
<tr>
<td>auto.commit.interval.ms</td>
<tdcolspan="1">60 * 1000</td>
<td>The frequency in ms that the consumer offsets are committed to zookeeper.</td>
</tr>
<tr>
<td>queued.max.message.chunks</td>
<tdcolspan="1">2</td>
<td>Max number of message chunks buffered for consumption. Each chunk can be up to fetch.message.max.bytes.</td>
</tr>
<tr>
<td>rebalance.max.retries</td>
<tdcolspan="1">4</td>
<td>When a new consumer joins a consumer group the set of consumers attempt to "rebalance" the load to assign partitions to each consumer. If the set of consumers changes while this assignment is taking place the rebalance will fail and retry. This setting controls the maximum number of attempts before giving up.</td>
</tr>
<tr>
<td>fetch.min.bytes</td>
<tdcolspan="1">1</td>
<td>The minimum amount of data the server should return for a fetch request. If insufficient data is available the request will wait for that much data to accumulate before answering the request.</td>
</tr>
<tr>
<td>fetch.wait.max.ms</td>
<tdcolspan="1">100</td>
<td>The maximum amount of time the server will block before answering the fetch request if there isn't sufficient data to immediately satisfy fetch.min.bytes</td>
</tr>
<tr>
<td>rebalance.backoff.ms</td>
<td>2000</td>
<td>Backoff time between retries during rebalance. If not set explicitly, the value in zookeeper.sync.time.ms is used.
</td>
</tr>
<tr>
<td>refresh.leader.backoff.ms</td>
<tdcolspan="1">200</td>
<td>Backoff time to wait before trying to determine the leader of a partition that has just lost its leader.</td>
</tr>
<tr>
<td>auto.offset.reset</td>
<tdcolspan="1">largest</td>
<td>
<p>What to do when there is no initial offset in ZooKeeper or if an offset is out of range:<br/>* smallest : automatically reset the offset to the smallest offset<br/>* largest : automatically reset the offset to the largest offset<br/>* anything else: throw exception to the consumer</p>
</td>
</tr>
<tr>
<td>consumer.timeout.ms</td>
<tdcolspan="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>
<tdcolspan="1">true</td>
<td>Whether messages from internal topics (such as offsets) should be exposed to the consumer.</td>
</tr>
<tr>
<td>client.id</td>
<tdcolspan="1">group id value</td>
<td>The client id is a user-specified string sent in each request to help trace calls. It should logically identify the application making the request.</td>
</tr>
<tr>
<td>zookeeper.session.timeout.ms</td>
<tdcolspan="1">6000</td>
<td>ZooKeeper session timeout. If the consumer fails to heartbeat to ZooKeeper for this period of time it is considered dead and a rebalance will occur.</td>
</tr>
<tr>
<td>zookeeper.connection.timeout.ms</td>
<tdcolspan="1">6000</td>
<td>The max time that the client waits while establishing a connection to zookeeper.</td>
</tr>
<tr>
<td>zookeeper.sync.time.ms</td>
<tdcolspan="1">2000</td>
<td>How far a ZK follower can be behind a ZK leader</td>
</tr>
<tr>
<td>offsets.storage</td>
<tdcolspan="1">zookeeper</td>
<td>Select where offsets should be stored (zookeeper or kafka).</td>
</tr>
<tr>
<td>offsets.channel.backoff.ms</td>
<tdcolspan="1">1000</td>
<td>The backoff period when reconnecting the offsets channel or retrying failed offset fetch/commit requests.</td>
</tr>
<tr>
<td>offsets.channel.socket.timeout.ms</td>
<tdcolspan="1">10000</td>
<td>Socket timeout when reading responses for offset fetch/commit requests. This timeout is also used for ConsumerMetadata requests that are used to query for the offset manager.</td>
</tr>
<tr>
<td>offsets.commit.max.retries</td>
<tdcolspan="1">5</td>
<td>Retry the offset commit up to this many times on failure. This retry count only applies to offset commits during shut-down. It does not apply to commits originating from the auto-commit thread. It also does not apply to attempts to query for the offset coordinator before committing offsets. i.e., if a consumer metadata request fails for any reason, it will be retried and that retry does not count toward this limit.</td>
</tr>
<tr>
<td>dual.commit.enabled</td>
<tdcolspan="1">true</td>
<td>If you are using "kafka" as offsets.storage, you can dual commit offsets to ZooKeeper (in addition to Kafka). This is required during migration from zookeeper-based offset storage to kafka-based offset storage. With respect to any given consumer group, it is safe to turn this off after all instances within that group have been migrated to the new version that commits offsets to the broker (instead of directly to ZooKeeper).</td>
</tr>
<tr>
<td>partition.assignment.strategy</td>
<tdcolspan="1">range</td>
<td><p>Select between the "range" or "roundrobin" strategy for assigning partitions to consumer streams.<p>The round-robin partition assignor lays out all the available partitions and all the available consumer threads. It then proceeds to do a round-robin assignment from partition to consumer thread. If the subscriptions of all consumer instances are identical, then the partitions will be uniformly distributed. (i.e., the partition ownership counts will be within a delta of exactly one across all consumer threads.) Round-robin assignment is permitted only if: (a) Every topic has the same number of streams within a consumer instance (b) The set of subscribed topics is identical for every consumer instance within the group.<p> Range partitioning works on a per-topic basis. For each topic, we lay out the available partitions in numeric order and the consumer threads in lexicographic order. We then divide the number of partitions by the total number of consumer streams (threads) to determine the number of partitions to assign to each consumer. If it does not evenly divide, then the first few consumers will have one extra partition.</td>
</tr>
</tbody>
</table>
<p>More details about consumer configuration can be found in the scala class <code>kafka.consumer.ConsumerConfig</code>.</p>
