log.cleaner.threads — Kafka Broker Configuration
The number of background threads to use for log cleaning.
Description
The number of background threads to use for log cleaning
Default Values by Kafka Version
| Kafka Version | Default Value |
|---|---|
| 0.8.1 | 1 |
| 0.8.2 | 1 |
| 0.9.0 | 1 |
| 0.10.0 | 1 |
| 0.10.1 | 1 |
| 0.10.2 | 1 |
| 0.11.0 | 1 |
| 1.0 | 1 |
| 1.1 | 1 |
| 2.0 | 1 |
| 2.1 | 1 |
| 2.2 | 1 |
| 2.3 | 1 |
| 2.4 | 1 |
| 2.5 | 1 |
| 2.6 | 1 |
| 2.7 | 1 |
| 2.8 | 1 |
| 3.0 | 1 |
| 3.1 | 1 |
| 3.2 | 1 |
| 3.3 | 1 |
| 3.4 | 1 |
| 3.5 | 1 |
| 3.6 | 1 |
| 3.7 | 1 |
| 3.8 | 1 |
| 3.9 | 1 |
| 4.0 | 1 |
| 4.1 | 1 |
| 4.2 | 1 |
Tuning Recommendation
| Profile | Recommended | Why |
|---|---|---|
| broker / cost | 2 | With log.cleanup.policy=compact, a single cleaner thread can fall behind on high-write-rate compacted topics, causing the dirty ratio to grow and increasing storage consumption. Two threads allow parallel compaction across different topic-partitions. |
Related Configs
log.cleaner.io.max.bytes.per.second · log.cleanup.policy · log.cleaner.dedupe.buffer.size · log.cleaner.min.cleanable.ratio
Manage Kafka configs across all your clusters with Conduktor Console — view, compare, and update configurations in one place.