Important

You are viewing documentation for an older version of Confluent Platform. For the latest, click here.

Broker Configurations¶

These topics provides configuration parameters available for Confluent Platform. The parameters are organized by order of importance, ranked from high to low.

High Importance¶

zookeeper.connect¶

ZooKeeper host string

Type: string
Importance: high
Dynamic Update Mode: read-only

advertised.host.name¶

DEPRECATED: only used when advertised.listeners or listeners are not set. Use advertised.listeners instead. 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().

Type: string
Default: null
Importance: high
Dynamic Update Mode: read-only

advertised.listeners¶

Listeners to publish to ZooKeeper for clients to use, if different than the listeners config property. 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. Unlike listeners it is not valid to advertise the 0.0.0.0 meta-address.

Type: string
Default: null
Importance: high
Dynamic Update Mode: per-broker

advertised.port¶

DEPRECATED: only used when advertised.listeners or listeners are not set. Use advertised.listeners instead. 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.

Type: int
Default: null
Importance: high
Dynamic Update Mode: read-only

auto.create.topics.enable¶

Enable auto creation of topic on the server

Type: boolean
Default: true
Importance: high
Dynamic Update Mode: read-only

auto.leader.rebalance.enable¶

Enables auto leader balancing. A background thread checks and triggers leader balance if required at regular intervals

Type: boolean
Default: true
Importance: high
Dynamic Update Mode: read-only

background.threads¶

The number of threads to use for various background processing tasks

Type: int
Default: 10
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: cluster-wide

broker.id¶

The broker ID for this server. If unset, a unique broker ID will be generated.To avoid conflicts between ZooKeeper generated broker ID’s and user configured broker ID’s, generated broker ids start from reserved.broker.max.id + 1.

Type: int
Default: -1
Importance: high
Dynamic Update Mode: read-only

compression.type¶

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.

Type: string
Default: producer
Importance: high
Dynamic Update Mode: cluster-wide

delete.topic.enable¶

Enables delete topic. Delete topic through the admin tool will have no effect if this config is turned off

Type: boolean
Default: true
Importance: high
Dynamic Update Mode: read-only

host.name¶

DEPRECATED: only used when listeners is not set. Use listeners instead. 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

Type: string “”
Importance: high
Dynamic Update Mode: read-only

kafka.metrics.polling.interval.secs¶

The metrics polling interval (in seconds) used in kafka.metrics.reporters implementations.

Type: int
Default: 10
Importance: low
Dynamic Update Mode: read-only

leader.imbalance.check.interval.seconds¶

The frequency with which the partition rebalance check is triggered by the controller

Type: long
Default: 300
Importance: high
Dynamic Update Mode: read-only

leader.imbalance.per.broker.percentage¶

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.

Type: int
Default: 10
Importance: high
Dynamic Update Mode: read-only

listeners¶

Comma-separated list of URIs we will listen on and the listener names. If the listener name is not a security protocol, listener.security.protocol.map must also be set. 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,SSL://:9091
CLIENT://0.0.0.0:9092,REPLICATION://localhost:9093

Type: string
Default: null
Importance: high
Dynamic Update Mode: per-broker

log.dir¶

The directory in which the log data is kept (supplemental for log.dirs property)

Type: string
Default: /tmp/kafka-logs
Importance: high
Dynamic Update Mode: read-only

log.dirs¶

The directories in which the log data is kept. If not set, the value in log.dir is used

Type: string
Default: null
Importance: high
Dynamic Update Mode: read-only

log.flush.interval.messages¶

The number of messages accumulated on a log partition before messages are flushed to disk

Type: long
Default: 9223372036854775807
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: cluster-wide

log.flush.interval.ms¶

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

Type: long
Default: null
Importance: high
Dynamic Update Mode: cluster-wide

log.flush.offset.checkpoint.interval.ms¶

The frequency with which we update the persistent record of the last flush which acts as the log recovery point

Type: int
Default: 60000
Valid Values: [0,…]
Importance: high
Dynamic Update Mode: read-only

log.flush.scheduler.interval.ms¶

The frequency in ms that the log flusher checks whether any log needs to be flushed to disk

Type: long
Default: 9223372036854775807
Importance: high
Dynamic Update Mode: read-only

log.flush.start.offset.checkpoint.interval.ms¶

The frequency with which we update the persistent record of log start offset

Type: int
Default: 60000
Valid Values: [0,…]
Importance: high
Dynamic Update Mode: read-only

log.retention.bytes¶

The maximum size of the log before deleting it

Type: long
Default: -1
Importance: high
Dynamic Update Mode: cluster-wide

log.retention.hours¶

The number of hours to keep a log file before deleting it (in hours), tertiary to log.retention.ms property

Type: int
Default: 168
Importance: high
Dynamic Update Mode: read-only

log.retention.minutes¶

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

Type: int
Default: null
Importance: high
Dynamic Update Mode: read-only

log.retention.ms¶

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

Type: long
Default: null
Importance: high
Dynamic Update Mode: cluster-wide

log.roll.hours¶

The maximum time before a new log segment is rolled out (in hours), secondary to log.roll.ms property

Type: int
Default: 168
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

log.roll.jitter.hours¶

The maximum jitter to subtract from logRollTimeMillis (in hours), secondary to log.roll.jitter.ms property

Type: int
Default: 0
Valid Values: [0,…]
Importance: high
Dynamic Update Mode: read-only

log.roll.jitter.ms¶

The maximum jitter to subtract from logRollTimeMillis (in milliseconds). If not set, the value in log.roll.jitter.hours is used

Type: long
Default: null
Importance: high
Dynamic Update Mode: cluster-wide

log.roll.ms¶

The maximum time before a new log segment is rolled out (in milliseconds). If not set, the value in log.roll.hours is used

Type: long
Default: null
Importance: high
Dynamic Update Mode: cluster-wide

log.segment.bytes¶

The maximum size of a single log file

Type: int
Default: 1073741824
Valid Values: [14,…]
Importance: high
Dynamic Update Mode: cluster-wide

log.segment.delete.delay.ms¶

The amount of time to wait before deleting a file from the filesystem

Type: long
Default: 60000
Valid Values: [0,…]
Importance: high
Dynamic Update Mode: cluster-wide

message.max.bytes¶

The largest record batch size allowed by Apache Kafka®. If this is increased and there are consumers older than 0.10.2, the consumers’ fetch size must also be increased so that the they can fetch record batches this large.

In the latest message format version, records are always grouped into batches for efficiency. In previous message format versions, uncompressed records are not grouped into batches and this limit only applies to a single record in that case.

This can be set per topic with the topic level max.message.bytes config.

Type: int
Default: 1000012
Valid Values: [0,…]
Importance: high
Dynamic Update Mode: cluster-wide

min.insync.replicas¶

When a producer sets acks to “all” (or “-1”), min.insync.replicas specifies the minimum number of replicas that must acknowledge a write for the write to be considered successful. If this minimum cannot be met, then the producer will raise an exception (either NotEnoughReplicas or NotEnoughReplicasAfterAppend).

When used together, min.insync.replicas and acks allow you to enforce greater durability guarantees. A typical scenario would be to create a topic with a replication factor of 3, set min.insync.replicas to 2, and produce with acks of “all”. This will ensure that the producer raises an exception if a majority of replicas do not receive a write.

Type: int
Default: 1
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: cluster-wide

num.io.threads¶

The number of threads that the server uses for processing requests, which may include disk I/O

Type: int
Default: 8
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: cluster-wide

num.network.threads¶

The number of threads that the server uses for receiving requests from the network and sending responses to the network

Type: int
Default: 3
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: cluster-wide

num.recovery.threads.per.data.dir¶

The number of threads per data directory to be used for log recovery at startup and flushing at shutdown

Type: int
Default: 1
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: cluster-wide

num.replica.alter.log.dirs.threads¶

The number of threads that can move replicas between log directories, which may include disk I/O

Type: int
Default: null
Importance: high
Dynamic Update Mode: read-only

num.replica.fetchers¶

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.

Type: int
Default: 1
Importance: high
Dynamic Update Mode: cluster-wide

offset.metadata.max.bytes¶

The maximum size for a metadata entry associated with an offset commit

Type: int
Default: 4096
Importance: high
Dynamic Update Mode: read-only

offsets.commit.required.acks¶

The required acks before the commit can be accepted. In general, the default (-1) should not be overridden

Type: short
Default: -1
Importance: high
Dynamic Update Mode: read-only

offsets.commit.timeout.ms¶

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.

Type: int
Default: 5000
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

offsets.load.buffer.size¶

Batch size for reading from the offsets segments when loading offsets into the cache.

Type: int
Default: 5242880
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

offsets.retention.check.interval.ms¶

Frequency at which to check for stale offsets

Type: int
Default: 600000
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

offsets.retention.minutes¶

Offsets older than this retention period will be discarded

Type: int
Default: 10080
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

offsets.topic.compression.codec¶

Compression codec for the offsets topic - compression may be used to achieve “atomic” commits

Type: int
Default: 0
Importance: high
Dynamic Update Mode: read-only

offsets.topic.num.partitions¶

The number of partitions for the offset commit topic (should not change after deployment)

Type: int
Default: 50
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

offsets.topic.replication.factor¶

The replication factor for the offsets topic (set higher to ensure availability). Internal topic creation will fail until the cluster size meets this replication factor requirement.

Type: short 3
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

offsets.topic.segment.bytes¶

The offsets topic segment bytes should be kept relatively small in order to facilitate faster log compaction and cache loads

Type: int
Default: 104857600
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

port¶

DEPRECATED: only used when listeners is not set. Use listeners instead. the port to listen and accept connections on

Type: int
Default: 9092
Importance: high
Dynamic Update Mode: read-only

queued.max.requests¶

The number of queued requests allowed before blocking the network threads

Type: int
Default: 500
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

quota.consumer.default¶

DEPRECATED: Used only when dynamic default quotas are not configured for <user, <client-id> or <user, client-id> in ZooKeeper. Any consumer distinguished by clientId/consumer group will get throttled if it fetches more bytes than this value per-second

Type: int
Default: 9223372036854775807
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

quota.producer.default¶

DEPRECATED: Used only when dynamic default quotas are not configured for <user>, <client-id> or <user, client-id> in ZooKeeper. Any producer distinguished by clientId will get throttled if it produces more bytes than this value per-second

Type: int
Default: 9223372036854775807
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

replica.fetch.min.bytes¶

Minimum bytes expected for each fetch response. If not enough bytes, wait up to replicaMaxWaitTimeMs

Type: int
Default: 1
Importance: high
Dynamic Update Mode: read-only

replica.fetch.wait.max.ms¶

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

Type: int
Default: 500
Importance: high
Dynamic Update Mode: read-only

replica.high.watermark.checkpoint.interval.ms¶

The frequency with which the high watermark is saved out to disk

Type: int
Default: 5000
Importance: high
Dynamic Update Mode: read-only

replica.lag.time.max.ms¶

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

Type: int
Default: 10000
Importance: high
Dynamic Update Mode: read-only

replica.socket.receive.buffer.bytes¶

The socket receive buffer for network requests

Type: int
Default: 65536
Importance: high
Dynamic Update Mode: read-only

replica.socket.timeout.ms¶

The socket timeout for network requests. Its value should be at least replica.fetch.wait.max.ms

Type: int
Default: 30000
Importance: high
Dynamic Update Mode: read-only

request.timeout.ms¶

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.

Type: int
Default: 30000
Importance: high
Dynamic Update Mode: read-only

socket.receive.buffer.bytes¶

The SO_RCVBUF buffer of the socket sever sockets. If the value is -1, the OS default will be used.

Type: int
Default: 102400
Importance: high
Dynamic Update Mode: read-only

socket.request.max.bytes¶

The maximum number of bytes in a socket request

Type: int
Default: 104857600
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

socket.send.buffer.bytes¶

The SO_SNDBUF buffer of the socket sever sockets. If the value is -1, the OS default will be used.

Type: int
Default: 102400
Importance: high
Dynamic Update Mode: read-only

transaction.max.timeout.ms¶

The maximum allowed timeout for transactions. If a client’s requested transaction time exceed this, then the broker will return an error in InitProducerIdRequest. This prevents a client from too large of a timeout, which can stall consumers reading from topics included in the transaction.

Type: int
Default: 900000
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

transaction.state.log.load.buffer.size¶

Batch size for reading from the transaction log segments when loading producer IDs and transactions into the cache.

Type: int
Default: 5242880
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

transaction.state.log.min.isr¶

Overridden min.insync.replicas config for the transaction topic.

Type: int
Default: 2
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

transaction.state.log.num.partitions¶

The number of partitions for the transaction topic (should not change after deployment).

Type: int
Default: 50
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

transaction.state.log.replication.factor¶

The replication factor for the transaction topic (set higher to ensure availability). Internal topic creation will fail until the cluster size meets this replication factor requirement.

Type: short 3
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

transaction.state.log.segment.bytes¶

The transaction topic segment bytes should be kept relatively small in order to facilitate faster log compaction and cache loads

Type: int
Default: 104857600
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

transactional.id.expiration.ms¶

The maximum amount of time in ms that the transaction coordinator will wait before proactively expire a producer’s transactional ID without receiving any transaction status updates from it.

Type: int
Default: 604800000
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

unclean.leader.election.enable¶

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

Type: boolean
Default: false
Importance: high
Dynamic Update Mode: cluster-wide

zookeeper.connection.timeout.ms¶

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.

Type: int
Default: null
Importance: high
Dynamic Update Mode: read-only

zookeeper.max.in.flight.requests¶

The maximum number of unacknowledged requests the client will send to ZooKeeper before blocking.

Type: int
Default: 10
Valid Values: [1,…]
Importance: high
Dynamic Update Mode: read-only

zookeeper.session.timeout.ms¶

ZooKeeper session timeout.

Type: int
Default: 6000
Importance: high
Dynamic Update Mode: read-only

zookeeper.set.acl¶

Set client to use secure ACLs.

Type: boolean
Default: false
Importance: high
Dynamic Update Mode: read-only

Medium Importance¶

broker.id.generation.enable¶

Enable automatic broker ID generation on the server. When enabled the value configured for reserved.broker.max.id should be reviewed.

Type: boolean
Default: true
Importance: medium
Dynamic Update Mode: read-only

broker.rack¶

Rack of the broker. This will be used in rack aware replication assignment for fault tolerance. Examples: RACK1, us-east-1d

Type: string
Default: null
Importance: medium
Dynamic Update Mode: read-only

connections.max.idle.ms¶

Idle connections timeout: the server socket processor threads close the connections that idle more than this

Type: int
Default: 600000
Importance: medium
Dynamic Update Mode: read-only

controlled.shutdown.enable¶

Enable controlled shutdown of the server

Type: boolean
Default: true
Importance: medium
Dynamic Update Mode: read-only

controlled.shutdown.max.retries¶

Controlled shutdown can fail for multiple reasons. This determines the number of retries when such failure happens

Type: int
Default: 3
Importance: medium
Dynamic Update Mode: read-only

controlled.shutdown.retry.backoff.ms¶

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.

Type: int
Default: 5000
Importance: medium
Dynamic Update Mode: read-only

controller.socket.timeout.ms¶

The socket timeout for controller-to-broker channels

Type: int
Default: 30000
Importance: medium
Dynamic Update Mode: read-only

default.replication.factor¶

default replication factors for automatically created topics

Type: int
Default: 1
Importance: medium
Dynamic Update Mode: read-only

delegation.token.expiry.time.ms¶

The token validity time in seconds before the token needs to be renewed. Default value 1 day.

Type: int
Default: 86400000
Valid Values: [1,…]
Importance: medium
Dynamic Update Mode: read-only

delegation.token.master.key¶

Master/secret key to generate and verify delegation tokens. Same key must be configured across all the brokers. If the key is not set or set to empty string, brokers will disable the delegation token support.

Type: password
Default: null
Importance: medium
Dynamic Update Mode: read-only

delegation.token.max.lifetime.ms¶

The token has a maximum lifetime beyond which it cannot be renewed anymore. Default value 7 days.

Type: int
Default: 604800000
Valid Values: [1,…]
Importance: medium
Dynamic Update Mode: read-only

delete.records.purgatory.purge.interval.requests¶

The purge interval (in number of requests) of the delete records request purgatory

Type: int
Default: 1
Importance: medium
Dynamic Update Mode: read-only

fetch.purgatory.purge.interval.requests¶

The purge interval (in number of requests) of the fetch request purgatory

Type: int
Default: 1000
Importance: medium
Dynamic Update Mode: read-only

group.initial.rebalance.delay.ms¶

The amount of time the group coordinator will wait for more consumers to join a new group before performing the first rebalance. A longer delay means potentially fewer rebalances, but increases the time until processing begins.

Type: int
Default: 3000
Importance: medium
Dynamic Update Mode: read-only

group.max.session.timeout.ms¶

The maximum allowed session timeout for registered consumers. Longer timeouts give consumers more time to process messages in between heartbeats at the cost of a longer time to detect failures.

Type: int
Default: 300000
Importance: medium
Dynamic Update Mode: read-only

group.min.session.timeout.ms¶

The minimum allowed session timeout for registered consumers. Shorter timeouts result in quicker failure detection at the cost of more frequent consumer heartbeating, which can overwhelm broker resources.

Type: int
Default: 6000
Importance: medium
Dynamic Update Mode: read-only

inter.broker.listener.name¶

Name of listener used for communication between brokers. If this is unset, the listener name is defined by security.inter.broker.protocol. It is an error to set this and security.inter.broker.protocol properties at the same time.

Type: string
Default: null
Importance: medium
Dynamic Update Mode: read-only

inter.broker.protocol.version¶

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 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.

Type: string
Default: 1.1-IV0
Importance: medium
Dynamic Update Mode: read-only

log.cleaner.backoff.ms¶

The amount of time to sleep when there are no logs to clean

Type: int
Default: 15000
Valid Values: [0,…]
Importance: medium
Dynamic Update Mode: cluster-wide

log.cleaner.dedupe.buffer.size¶

The total memory used for log deduplication across all cleaner threads

Type: int
Default: 134217728
Importance: medium
Dynamic Update Mode: cluster-wide

log.cleaner.delete.retention.ms¶

Determines how long delete records are retained.

Type: int
Default: 86400000
Importance: medium
Dynamic Update Mode: cluster-wide

log.cleaner.enable¶

Enable the log cleaner process to run on the server. Should be enabled if using any topics with a cleanup.policy=compact including the internal offsets topic. If disabled those topics will not be compacted and continually grow in size.

Type: boolean
Default: true
Importance: medium
Dynamic Update Mode: read-only

log.cleaner.io.buffer.load.factor¶

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 double 0.9 - Importance: medium - Dynamic Update Mode: cluster-wide

log.cleaner.io.buffer.size¶

The total memory used for log cleaner I/O buffers across all cleaner threads

Type: int
Default: 524288
Valid Values: [0,…]
Importance: medium
Dynamic Update Mode: cluster-wide

log.cleaner.io.max.bytes.per.second¶

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 double 1.7976931348623157E308.

Importance: medium
Dynamic Update Mode: cluster-wide

log.cleaner.min.cleanable.ratio¶

The minimum ratio of dirty log to total log for a log to eligible for cleaning.

Type: double 0.5
Importance: medium
Dynamic Update Mode: cluster-wide

log.cleaner.min.compaction.lag.ms¶

The minimum time a message will remain uncompacted in the log. Only applicable for logs that are being compacted.

Type: long
Default: 0
Importance: medium
Dynamic Update Mode: cluster-wide

log.cleaner.threads¶

The number of background threads to use for log cleaning

Type: int
Default: 1
Valid Values: [0,…]
Importance: medium
Dynamic Update Mode: cluster-wide

log.cleanup.policy¶

The default cleanup policy for segments beyond the retention window. A comma separated list of valid policies. Valid policies are: delete and compact.

Type: list
Default: delete
Valid Values: [compact, delete]
Importance: medium
Dynamic Update Mode: cluster-wide

log.index.interval.bytes¶

The interval with which we add an entry to the offset index.

Type: int
Default: 4096
Valid Values: [0,…]
Importance: medium
Dynamic Update Mode: cluster-wide

log.index.size.max.bytes¶

The maximum size in bytes of the offset index.

Type: int
Default: 10485760 [4,…]
Importance: medium
Dynamic Update Mode: cluster-wide

log.message.format.version¶

Specify the message format version the broker will use to append messages to the logs. The value should be a valid ApiVersion. Some examples are: 0.8.2, 0.9.0.0, 0.10.0, check ApiVersion for more details. By setting a particular message format version, the user is certifying that all the existing messages on disk are smaller or equal than the specified version. Setting this value incorrectly will cause consumers with older versions to break as they will receive messages with a format that they don’t understand.

Type: string
Default: 1.1-IV0
Importance: medium
Dynamic Update Mode: read-only

log.message.timestamp.difference.max.ms¶

The maximum difference allowed between the timestamp when a broker receives a message and the timestamp specified in the message. If log.message.timestamp.type=CreateTime, a message will be rejected if the difference in timestamp exceeds this threshold. This configuration is ignored if log.message.timestamp.type=LogAppendTime.The maximum timestamp difference allowed should be no greater than log.retention.ms to avoid unnecessarily frequent log rolling.

Type: int
Default: 9223372036854775807
Importance: medium
Dynamic Update Mode: cluster-wide

log.message.timestamp.type¶

Define whether the timestamp in the message is message create time or log append time. The value should be either CreateTime or LogAppendTime.

Type: string
Default: CreateTime [CreateTime, LogAppendTime]
Importance: medium
Dynamic Update Mode: cluster-wide

log.preallocate¶

Indicates whether to preallocate file when creating new segment. If you are using Kafka on Windows, you probably need to set it to true.

Type: boolean
Default: false
Importance: medium
Dynamic Update Mode: cluster-wide

log.retention.check.interval.ms¶

The frequency in milliseconds that the log cleaner checks whether any log is eligible for deletion.

Type: int
Default: 300000
Valid Values: [1,…]
Importance: medium
Dynamic Update Mode: read-only

max.connections.per.ip¶

The maximum number of connections allowed from each IP address.

Type: int
Default: 2147483647
Valid Values: [1,…]
Importance: medium
Dynamic Update Mode: read-only

max.connections.per.ip.overrides¶

Per-IP or hostname overrides to the default maximum number of connections.

Type: string
Default: “”
Importance: medium
Dynamic Update Mode: read-only

max.incremental.fetch.session.cache.slots¶

The maximum number of incremental fetch sessions that are maintained.

Type: int
Default: 1000
Valid Values: [0,…]
Importance: medium
Dynamic Update Mode: read-only

num.partitions¶

The default number of log partitions for auto-created topics. You should increase this since it is better to over-partition a topic. Over-partitioning a topic leads to better data balancing and aids consumer parallelism. For keyed data, you should avoid changing the number of partitions in a topic.

Type: int
Default: 1
Valid Values: [1,…]
Importance: medium
Dynamic Update Mode: read-only

password.encoder.old.secret¶

The old secret that was used for encoding dynamically configured passwords. This is required only when the secret is updated. If specified, all dynamically encoded passwords are decoded using this old secret and re-encoded using password.encoder.secret when broker starts up.

Type: password
Default: null
Importance: medium
Dynamic Update Mode: read-only

password.encoder.secret¶

The secret used for encoding dynamically configured passwords for this broker.

Type: password
Default: null
Importance: medium
Dynamic Update Mode: read-only

principal.builder.class¶

The fully qualified name of a class that implements the KafkaPrincipalBuilder interface, which is used to build the KafkaPrincipal object used during authorization. This config also supports the deprecated PrincipalBuilder interface which was previously used for client authentication over SSL. If no principal builder is defined, the default behavior depends on the security protocol in use. For SSL authentication, the principal name will be the distinguished name from the client certificate if one is provided; otherwise, if client authentication is not required, the principal name will be ANONYMOUS. For SASL authentication, the principal will be derived using the rules defined by sasl.kerberos.principal.to.local.rules if GSSAPI is in use, and the SASL authentication ID for other mechanisms. For PLAINTEXT, the principal will be ANONYMOUS.

Type: class
Default: null
Importance: medium
Dynamic Update Mode: per-broker

producer.purgatory.purge.interval.requests¶

The purge interval (in number of requests) of the producer request purgatory.

Type: int
Default: 1000
Importance: medium
Dynamic Update Mode: read-only

queued.max.request.bytes¶

The number of queued bytes allowed before no more requests are read.

Type: long
Default: -1
Importance: medium
Dynamic Update Mode: read-only

replica.fetch.backoff.ms¶

The amount of time to sleep when fetch partition error occurs.

Type: int
Default: 1000
Valid Values: [0,…]
Importance: medium
Dynamic Update Mode: read-only

replica.fetch.max.bytes¶

The number of bytes of messages to attempt to fetch for each partition. This is not an absolute maximum, if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that progress can be made. The maximum record batch size accepted by the broker is defined via message.max.bytes (broker config) or max.message.bytes (topic config).

Type: int
Default: 1048576
Valid Values: [0,…]
Importance: medium
Dynamic Update Mode: read-only

replica.fetch.response.max.bytes¶

Maximum bytes expected for the entire fetch response. Records are fetched in batches, and if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that progress can be made. As such, this is not an absolute maximum. The maximum record batch size accepted by the broker is defined via message.max.bytes (broker config) or max.message.bytes (topic config).

Type: int
Default: 10485760
Valid Values: [0,…]
Importance: medium
Dynamic Update Mode: read-only

reserved.broker.max.id¶

Max number that can be used for a broker.id.

Type: int
Default: 1000
Valid Values: [0,…]
Importance: medium
Dynamic Update Mode: read-only

sasl.enabled.mechanisms¶

The list of SASL mechanisms enabled in the Kafka server. The list may contain any mechanism for which a security provider is available. Only GSSAPI is enabled by default.

Type: list
Default: GSSAPI
Importance: medium
Dynamic Update Mode: per-broker

sasl.jaas.config¶

JAAS login context parameters for SASL connections in the format used by JAAS configuration files. JAAS configuration file format is described here. The format for the value is: <loginModuleClass> <controlFlag> (<optionName>=<optionValue>)*;.

Type: password
Default: null
Importance: medium
Dynamic Update Mode: per-broker

sasl.kerberos.kinit.cmd¶

Kerberos kinit command path.

Type: string
Default: /usr/bin/kinit
Importance: medium
Dynamic Update Mode: per-broker

sasl.kerberos.min.time.before.relogin¶

Login thread sleep time between refresh attempts.

Type: long
Default: 60000
Importance: medium
Dynamic Update Mode: per-broker

sasl.kerberos.principal.to.local.rules¶

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}. For more details on the format please see security authorization and ACLs. Note that this configuration is ignored if an extension of KafkaPrincipalBuilder is provided by the principal.builder.class configuration.

Type: list
Default: DEFAULT
Importance: medium
Dynamic Update Mode: per-broker

sasl.kerberos.service.name¶

The Kerberos principal name that Kafka runs as. This can be defined either in Kafka’s JAAS config or in Kafka’s config.

Type: string
Default: null
Importance: medium
Dynamic Update Mode: per-broker

sasl.kerberos.ticket.renew.jitter¶

Percentage of random jitter added to the renewal time.

Type: double
Default: 0.05
Importance: medium
Dynamic Update Mode: per-broker

sasl.kerberos.ticket.renew.window.factor¶

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.

Type: double
Default: 0.8
Importance: medium
Dynamic Update Mode: per-broker

sasl.mechanism.inter.broker.protocol¶

SASL mechanism used for inter-broker communication. Default is GSSAPI.

Type: string
Default: GSSAPI
Importance: medium
Dynamic Update Mode: per-broker

security.inter.broker.protocol¶

Security protocol used to communicate between brokers. Valid values are: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL. It is an error to set this and inter.broker.listener.name properties at the same time.

Type: string
Default: PLAINTEXT
Importance: medium
Dynamic Update Mode: read-only

ssl.cipher.suites¶

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.

Type: list
Default: “”
Importance: medium
Dynamic Update Mode: per-broker

ssl.client.auth¶

Configures kafka broker to request client authentication. The following settings are common:

ssl.client.auth=required If set to required client authentication is required.
ssl.client.auth=requested This means client authentication is optional. unlike requested , if this option is set client can choose not to provide authentication information about itself
ssl.client.auth=none This means client authentication is not needed.
Type: string
Default: none
Valid Values: [required, requested, none]
Importance: medium
Dynamic Update Mode: per-broker

ssl.enabled.protocols¶

The list of protocols enabled for SSL connections.

Type: list
Default: TLSv1.2,TLSv1.1,TLSv1
Importance: medium
Dynamic Update Mode: per-broker

ssl.key.password¶

The password of the private key in the key store file. This is optional for client.

Type: password
Default: null
Importance: medium
Dynamic Update Mode: per-broker

ssl.keymanager.algorithm¶

The algorithm used by key manager factory for SSL connections. Default value is the key manager factory algorithm configured for the Java Virtual Machine.

Type: string
Default: SunX509
Importance: medium
Dynamic Update Mode: per-broker

ssl.keystore.location¶

The location of the key store file. This is optional for client and can be used for two-way authentication for client.

Type: string
Default: null
Importance: medium
Dynamic Update Mode: per-broker

ssl.keystore.password¶

The store password for the key store file. This is optional for client and only needed if ssl.keystore.location is configured.

Type: password
Default: null
Importance: medium
Dynamic Update Mode: per-broker

ssl.keystore.type¶

The file format of the key store file. This is optional for client.

Type: string
Default: JKS
Importance: medium
Dynamic Update Mode: per-broker

ssl.protocol¶

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.

Type: string
Default: TLS
Importance: medium
Dynamic Update Mode: per-broker

ssl.provider¶

The name of the security provider used for SSL connections. Default value is the default security provider of the JVM.

Type: string
Default: null
Importance: medium
Dynamic Update Mode: per-broker

ssl.trustmanager.algorithm¶

The algorithm used by trust manager factory for SSL connections. Default value is the trust manager factory algorithm configured for the Java Virtual Machine.

Type: string
Default: PKIX
Importance: medium
Dynamic Update Mode: per-broker

ssl.truststore.location¶

The location of the trust store file.

Type: string
Default: null
Importance: medium
Dynamic Update Mode: per-broker

ssl.truststore.password¶

The password for the trust store file. If a password is not set access to the truststore is still available, but integrity checking is disabled.

Type: password
Default: null
Importance: medium
Dynamic Update Mode: per-broker

ssl.truststore.type¶

The file format of the trust store file.

Type: string
Default: JKS
Importance: medium
Dynamic Update Mode: per-broker

Low Importance¶

alter.config.policy.class.name¶

The alter configs policy class that should be used for validation. The class should implement the org.apache.kafka.server.policy.AlterConfigPolicy interface.

Type: class
Default: null
Importance: low
Dynamic Update Mode: read-only

alter.log.dirs.replication.quota.window.num¶

The number of samples to retain in memory for alter log dirs replication quotas

Type: int
Default: 11
Valid Values: [1,…]
Importance: low
Dynamic Update Mode: read-only

alter.log.dirs.replication.quota.window.size.seconds¶

The time span of each sample for alter log dirs replication quotas

Type: int
Default: 1
Valid Values: [1,…]
Importance: low
Dynamic Update Mode: read-only

authorizer.class.name¶

The authorizer class to be used for authorization.

Tip

For more information, see Configuring the LDAP Authorizer and Authorization and ACLs.

Type: string “”
Importance: low
Dynamic Update Mode: read-only

create.topic.policy.class.name¶

The create topic policy class that should be used for validation. The class should implement the org.apache.kafka.server.policy.CreateTopicPolicy interface.

Type: class
Default: null
Importance: low
Dynamic Update Mode: read-only

delegation.token.expiry.check.interval.ms¶

Scan interval to remove expired delegation tokens.

Type: int
Default: 3600000
Valid Values: [1,…]
Importance: low
Dynamic Update Mode: read-only

listener.security.protocol.map¶

Map between listener names and security protocols. This must be defined for the same security protocol to be usable in more than one port or IP. For example, internal and external traffic can be separated even if SSL is required for both. Concretely, the user could define listeners with names INTERNAL and EXTERNAL and this property as: INTERNAL:SSL,EXTERNAL:SSL. As shown, key and value are separated by a colon and map entries are separated by commas. Each listener name should only appear once in the map. Different security (SSL and SASL) settings can be configured for each listener by adding a normalised prefix (the listener name is lowercased) to the config name. For example, to set a different keystore for the INTERNAL listener, a config with name listener.name.internal.ssl.keystore.location would be set. If the config for the listener name is not set, the config will fallback to the generic config (i.e. ssl.keystore.location).

Type: string
Default: PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL
Importance: low
Dynamic Update Mode: per-broker

metric.reporters¶

A list of classes to use as metrics reporters. Implementing the org.apache.kafka.common.metrics.MetricsReporter interface allows plugging in classes that will be notified of new metric creation. The JmxReporter is always included to register JMX statistics.

Type: list
Default: “”
Importance: low
Dynamic Update Mode: cluster-wide

metrics.num.samples¶

The number of samples maintained to compute metrics.

Type: int
Default: 2
Valid Values: [1,…]
Importance: low
Dynamic Update Mode: read-only

metrics.recording.level¶

The highest recording level for metrics.

Type: string
Default: INFO
Importance: low
Dynamic Update Mode: read-only

metrics.sample.window.ms¶

The window of time a metrics sample is computed over.

Type: int
Default: 30000
Valid Values: [1,…]
Importance: low
Dynamic Update Mode: read-only

password.encoder.cipher.algorithm¶

The Cipher algorithm used for encoding dynamically configured passwords.

Type: string
Default: AES/CBC/PKCS5Padding
Importance: low
Dynamic Update Mode: read-only

password.encoder.iterations¶

The iteration count used for encoding dynamically configured passwords.

Type: int
Default: 4096 [1024,…]
Importance: low
Dynamic Update Mode: read-only

password.encoder.key.length¶

The key length used for encoding dynamically configured passwords.

Type: int
Default: 128 [8,…]
Importance: low
Dynamic Update Mode: read-only

password.encoder.keyfactory.algorithm¶

The SecretKeyFactory algorithm used for encoding dynamically configured passwords. Default is PBKDF2WithHmacSHA512 if available and PBKDF2WithHmacSHA1 otherwise.

Type: string
Default: null
Importance: low
Dynamic Update Mode: read-only

quota.window.num¶

The number of samples to retain in memory for client quotas

Type: int
Default: 11
Valid Values: [1,…]
Importance: low
Dynamic Update Mode: read-only

quota.window.size.seconds¶

The time span of each sample for client quotas

Type: int
Default: 1
Valid Values: [1,…]
Importance: low
Dynamic Update Mode: read-only

replication.quota.window.num¶

The number of samples to retain in memory for replication quotas

Type: int
Default: 11
Valid Values: [1,…]
Importance: low
Dynamic Update Mode: read-only

replication.quota.window.size.seconds¶

The time span of each sample for replication quotas

Type: int
Default: 1
Valid Values: [1,…]
Importance: low
Dynamic Update Mode: read-only

ssl.endpoint.identification.algorithm¶

The endpoint identification algorithm to validate server hostname using server certificate.

Type: string
Default: null
Importance: low
Dynamic Update Mode: per-broker

ssl.secure.random.implementation¶

The SecureRandom PRNG implementation to use for SSL cryptography operations.

Type: string
Default: null
Importance: low
Dynamic Update Mode: per-broker

transaction.abort.timed.out.transaction.cleanup.interval.ms¶

The interval at which to rollback transactions that have timed out

Type: int
Default: 60000
Valid Values: [1,…]
Importance: low
Dynamic Update Mode: read-only

transaction.remove.expired.transaction.cleanup.interval.ms¶

The interval at which to remove transactions that have expired due to transactional.id.expiration.ms passing

Type: int
Default: 3600000
Valid Values: [1,…]
Importance: low
Dynamic Update Mode: read-only

zookeeper.sync.time.ms¶

How far a ZooKeeper follower can be behind a ZooKeeper leader

Type: int
Default: 2000
Importance: low
Dynamic Update Mode: read-only