Skip to content

Kafka broker configuration

Kafka broker configuration is primarily managed through the server.properties file.^[600-developer__big-data__Kafka__kafka-01.md] This configuration defines the broker's identity, storage locations, topic defaults, and cluster connections.

Core Identity Settings

Every broker in a cluster must be assigned a unique integer identifier.^[600-developer__big-data__Kafka__kafka-01.md] This is configured using the broker.id property.^[600-developer__big-data__Kafka__kafka-01.md]

Storage and Topic Defaults

The location where the broker stores log files is specified by the log.dirs property.^[600-developer__big-data__Kafka__kafka-01.md] For topics created without an explicit partition count, the broker applies a default value set by num.partitions^[600-developer__big-data__Kafka__kafka-01.md]; increasing this number allows for greater parallelism in consumption but results in more files across the brokers^[600-developer__big-data__Kafka__kafka-01.md].

Cluster and Topic Management

To connect with the cluster's metadata service, the broker requires a zookeeper.connect string^[600-developer__big-data__Kafka__kafka-01.md]. This string is formatted as a comma-separated list of host:port pairs^[600-developer__big-data__Kafka__kafka-01.md].

Additionally, the ability to delete topics is controlled by the delete.topic.enable configuration^[600-developer__big-data__Kafka__kafka-01.md]. Setting this to true allows topics to be removed from the cluster^[600-developer__big-data__Kafka__kafka-01.md].

Sources

  • 600-developer__big-data__Kafka__kafka-01.md